Content management system and content management program

Abstract

To provide a content management system that enables centralized management through a database of various managed objects while ensuring user convenience.SOLUTION: A content management system comprises a terminal device which accepts user operations, and a server connected to the terminal device. The server accepts input of file content for registering electronic files and file attribute information regarding the electronic files or record content for registering management attribute information regarding a desired managed object, registers and manages the input file content or record content in a database, and further registers the input file content or record content as content subordinate to the record content registered in the database in response to a user request.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a technique for managing various managed objects including electronic files using a database. [Background technology]

[0002] Conventionally, various techniques have been proposed for recording and managing electronic files in a database. For example, Patent Document 1 discloses an electronic document management device that aims to improve the efficiency of managing electronic documents that require authentication. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-140863 A Summary of the Invention [Problem to be solved by the invention]

[0004] In companies and organizations, electronic files created in each department are generally managed centrally in a specified database. However, in some cases, companies and organizations store and manage not only electronic files but also paper documents, samples, and other items. For this reason, there is a need for companies and organizations to centrally manage not only electronic files but also information for managing these management targets.

[0005] In conventional systems, when managing these managed objects, users had to take their own measures, such as creating and recording management ledgers as electronic files. This resulted in a high degree of freedom in the management method, which led to issues with the management situation becoming complicated. Another issue was that the searchability in the database differed depending on whether the file was electronic or not.

[0006] One object of the present disclosure is to provide a technology that enables centralized management of various managed objects, including electronic files, using a database while ensuring user convenience, in consideration of the above-mentioned problems. [Means for solving the problem]

[0007] A first aspect of the present disclosure relates to a content management system.

[0008] A content management system according to a first aspect includes a terminal device that accepts user operations, and a server that is connected to the terminal device. The server is configured to execute the following first to third processes. The first process is a process of accepting, via the terminal device, input of file content for registering an electronic file and file attribute information related to the electronic file, or record content for registering management attribute information related to a desired management target. The second process is a process of registering the input file content or record content in a database and managing it. The third process is a process of further registering, in response to a user request, the input file content or record content as sub-content subordinate to a base record content selected from the record contents registered in the database.

[0009] A second aspect of the present disclosure relates to a content management program that causes a computer to manage content.

[0010] A content management program according to a second aspect is configured to cause a computer to execute the following first to third processes. The first process is a process of accepting input of file content for registering an electronic file and file attribute information related to the electronic file, or record content for registering management attribute information related to a desired management object. The second process is a process of registering the input file content or record content in a database and managing it. The third process is a process of further registering, in response to a request, the input file content or record content as sub-content subordinate to a base record content selected from the record contents registered in the database. Effect of the Invention

[0011] According to the present disclosure, it is possible to centrally manage various management objects including electronic files using a database while ensuring user convenience. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a content management system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of a configuration of a database managed in the content management system according to the embodiment. [Diagram 3] FIG. 2 is a diagram showing a first example of management by a content management system according to an embodiment. [Figure 4] FIG. 11 is a diagram showing a second example of management by the content management system according to the embodiment. [Diagram 5] FIG. 11 is a diagram showing a third example of management by the content management system according to the embodiment. [Figure 6] 11 is a diagram for explaining a process executed by a server according to an embodiment with respect to a viewing and editing function. FIG. [Figure 7] FIG. 13 is a diagram showing an example of a display of a management screen relating to a viewing and editing function. [Figure 8]FIG. 13 is a diagram showing an example of a display of a management screen relating to a viewing and editing function. [Figure 9] FIG. 13 is a diagram showing an example of a display of a management screen relating to a viewing and editing function. [Figure 10] FIG. 13 is a diagram showing an example of a display of a management screen relating to a viewing and editing function. [Figure 11] FIG. 2 is a diagram for explaining a process executed by a server according to an embodiment with respect to a content registration function. [Figure 12] FIG. 13 is a diagram showing an example of a display of a management screen related to a content registration function. [Figure 13] FIG. 13 is a diagram showing an example of a display of a management screen related to a virtual directory search function. [Figure 14] FIG. 13 is a diagram for explaining an overview of a virtual directory search function. [Figure 15] 11 is a diagram for explaining a process executed by a server according to an embodiment with respect to a virtual directory search function. FIG. [Figure 16] FIG. 13 is a diagram showing an example of a display of a management screen related to a virtual directory search function. [Figure 17] 11 is a diagram for explaining a process executed by a server according to an embodiment with respect to a request function. FIG. [Figure 18] FIG. 2 is a diagram illustrating an example of a hardware configuration of a server according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment will be described with reference to the drawings.

[0014] 1. Content Management System 1 is a diagram showing an example of the configuration of a content management system 10 according to this embodiment. In this embodiment, the content management system 10 is a system operated between a management company and a user company. However, as will be understood from the following explanation, the subject of operation can be changed as appropriate depending on the environment to which the content management system 10 is applied.

[0015] It is considered that many electronic files that require management are created in a user company in relation to its business or activities. It is also considered that the user company uses the internal warehouse 210 owned by the user company to store items that require management. Alternatively, it is also considered that the user company uses the external warehouse 310 owned by the management business operator to store items that require management. Examples of items (hereinafter also referred to as "stored items") stored in the internal warehouse 210 or the external warehouse 310 include paper documents, papers, materials, recording media (USB memory, optical disks, magnetic disks, magnetic tapes, microfilms, etc.), various samples such as biological samples (cells, specimens, blood, medicines), etc. The content management system 10 provides a function for the user company to effectively manage such electronic files and items that require management.

[0016] The content management system 10 according to this embodiment is composed of a server 100 that manages a database D10, a terminal device 200 of a user company, and a terminal device 300 of a management company. The server 100, the terminal device 200, and the terminal device 300 are connected to each other via a communication network 1 so that they can transmit and receive information to each other. The communication network 1 is composed of, for example, the Internet or a local area network. The terminal device 200 and the terminal device 300 are composed of computers including a memory and a processor. A user 2 of the user company uses the functions of the content management system 10 by operating the terminal device 200. The functions of the content management system 10 are realized by the server 100 executing processing.

[0017] The server 100 is configured to accept input of content to be registered in the database D10 from the user 2 via the terminal device 200. The content relates to a management target that the user 2 needs to manage, as described below. The user 2 inputs the content by operating the terminal device 200. The server 100 then registers the input content in the database D10 and manages it.

[0018] In this embodiment, the content that the server 100 accepts as input is classified as file content or record content.

[0019] File content is content for registering electronic files and attribute information related to electronic files (hereinafter also referred to as "file attribute information"). One file content corresponds to one electronic file to be managed. However, the file content may be in a state in which only either the electronic file or the file attribute information is registered. The format of the electronic file is not particularly limited. For example, the electronic file may be a text file, a spreadsheet file, an audio file, an image file, a video file, etc.

[0020] The file attribute information is composed of one or more attribute items and attribute values ​​for each attribute item. The file attribute information serves as a keyword when searching for content on the database D10. The file attribute information can also be considered as a "tag" for the corresponding electronic file.

[0021] Record content is content for registering attribute information (hereinafter also referred to as "management attribute information") related to a desired management object. Unlike file content, electronic files are not registered in record content. In other words, record content is not intended to manage electronic files themselves. Possible management objects related to record content include groups of electronic files, stored items, groups of stored items, etc. For example, when the management object is a group of electronic files, one record content can be considered to correspond to one folder in a file system.

[0022] Like file attribute information, the management attribute information is composed of one or more attribute items and attribute values ​​for each attribute item. The management attribute information also serves as a keyword when searching for content in the database D10. The management attribute information can also be considered as a "tag" for the corresponding managed object.

[0023] The record content can be set as a content (hereinafter referred to as "item content") in which the management object is a stored item. The server 100 sets the specified record content as item content in response to a request from the user 2. In addition to the management attribute information, information on the storage status of the stored item (hereinafter also referred to as "item storage information") can be further registered in the record content set as the item content. The item storage information can include, for example, information such as the storage form, storage expiration date, storage location, and storage state of the stored item.

[0024] Furthermore, the server 100 can register the input file content or record content as sub-content subordinate to content (hereinafter also referred to as "base record content") selected from the record contents registered in the database D10 in response to a request from the user 2. That is, in the database D10, each record content can have one or more sub-contents.

[0025] Here, consider a case where the base record content and its sub-contents are set as product contents. In this case, the server 100 can further register a part or all of the product storage information set in the base record content as inherited to the sub-contents in response to a request from the user 2.

[0026] By the user 2 inputting the content in this manner, the server 100 manages a database D10 made up of file content, record content, and sub-content subordinate to the record content.

[0027] Fig. 2 is a diagram showing an example of the configuration of a database D10. Four record contents RC1, RC2, RC3, and RC4 and one file content FC1 are registered in the database D10 shown in Fig. 2. In particular, the record contents RC2 and RC3 and the file content FC1 are registered as sub-contents with the record content RC1 as the base record content. Furthermore, the record content RC4 is registered as sub-contents with the record content RC3 as the base record content. Furthermore, the record contents RC3 and RC4 are set as product contents.

[0028] Management attribute information is registered in each of the record contents RC1, RC2, RC3, and RC4. Furthermore, electronic files and file attribute information are registered in the file content FC1. Furthermore, item storage information is registered in each of the record contents RC3 and RC4, which are set as item contents. In particular, the server 100 inherits and registers the item storage information registered in the record content RC3 in the record content RC4.

[0029] As shown in FIG. 2, the database D10 according to this embodiment has a directory structure (hierarchical structure) in which sub-contents are subordinate to the record content RC. When focusing on the directory structure below, the terms first layer, second layer, ... are used for the contents registered in the database D10. The first layer is a layer of contents that have no subordinates. The second layer is a layer of sub-contents that are subordinate to the contents in the first layer. Similarly, the third layer, fourth layer, ... are defined below. For example, in the case shown in FIG. 2, the record content RC1 is the content in the first layer. Moreover, the record contents RC2 and RC3 and the file content FC1 are the content in the second layer. Moreover, the record content RC4 is the content in the third layer.

[0030] As described above, the server 100 receives content input from the user 2 and executes the process of configuring and managing the database D10. The user 2 can manage electronic files and items that require management by registering file content FC or record content RC in the database D10. Below, several examples of management by the content management system 10 will be described.

[0031] 1.1 First Example 3 is a diagram showing a first example of management by the content management system 10. The first example is a case where the content management system 10 performs folder management of electronic files.

[0032] Assume now that User 2 wishes to manage the electronic file "Contract1.pdf" in a folder, as shown in the upper part of Fig. 3. In this case, User 2 can perform the desired folder management by registering each content in database D10, as shown in the lower part of Fig. 3.

[0033] Specifically, first, user 2 registers record content RC11 corresponding to the folder "2023" in database D10. Next, user 2 registers record content RC12 corresponding to the folder "A0001" and record content RC13 corresponding to the folder "A0002" in database D10 as subcontents of record content RC11. Then, user 2 registers file content FC11 corresponding to "contract1.pdf" in database D10 as subcontents of record content RC12. "contract1.pdf", which is an electronic file, is registered in file content FC11. User 2 can also register file attribute information, which has attribute items such as contractor, contract date, and contract product, in file content FC11 in relation to "contract1.pdf".

[0034] In this way, according to the content management system 10, the user 2 can manage folders of electronic files using procedures that are almost the same as conventional folder management. The user 2 can also register file attribute information to the file content FC. By registering the file attribute information, the searchability of the target file content FC can be improved. Furthermore, the user 2 can also register management attribute information to the record content RC corresponding to the folder. By registering the management attribute information, the searchability of the record content RC corresponding to the folder can also be improved.

[0035] 1.2 Second Example 4 is a diagram showing a second example of management by the content management system 10. The second example is a case where the content management system 10 manages stored items.

[0036] Assume now that user 2 is storing "document box 1" in the internal warehouse 210 and "document box 2" in the external warehouse 310, as shown in the upper part of Fig. 4. Assume also that "document file 1" and "document file 2" are stored in "document box 1," and "document file 3" is stored in "document box 2." In this case, user 2 can manage the items stored in the internal warehouse 210 and the external warehouse 310 on the database D10 by registering each piece of content in the database D10, as shown in the lower part of Fig. 4.

[0037] Specifically, the user 2 first registers the record content RC21 corresponding to the "document box 1" and the record content RC22 corresponding to the "document box 2" in the database D10. In particular, the user 2 sets the record content RC21 and the record content RC22 as the item content. The user 2 then registers in the record content RC21 that the storage location is the internal warehouse 210 as the item storage information, and registers in the record content RC22 that the storage location is the external warehouse 310 as the item storage information. The user 2 can also register more detailed information about the storage location, such as the number of a cabinet in the warehouse, as the item storage information. In addition, the user 2 can also register the storage form, storage expiration date, and the like as the item storage information. Furthermore, the user 2 can also register management attribute information in which the type, contents, and the like of the stored item are attribute items in the record content RC21 and the record content RC22.

[0038] Next, the user 2 registers the record content RC23 corresponding to the "document file 1" and the record content RC24 corresponding to the "document file 2" in the database D10 as subcontents of the record content RC21. The user 2 also registers the record content RC25 corresponding to the "document file 3" in the database D10 as subcontents of the record content RC22. In particular, the user 2 sets the record content RC23, the record content RC24, and the record content RC25 as the item content. The user 2 then registers the item storage information in the record content RC23 and the record content RC24 that the storage location is the internal warehouse 210. Here, the user 2 can inherit and register the item storage information registered in the record content RC21 in each of the record content RC23 and the record content RC24. Similarly, the user 2 inherits and registers the item storage information registered in the record content RC22 in the record content RC25.

[0039] In this way, according to the content management system 10, the user 2 can manage the stored items stored in the internal warehouse 210 and the external warehouse 310 on the database D10 by registering the record content RC. Furthermore, the user 2 can manage the storage status of the corresponding stored item by registering item storage information in the record content RC. In particular, the user 2 can inherit and register the item storage information registered in the base record content in the sub-content. This can reduce the effort required to register the item storage information. Furthermore, the user 2 can improve the searchability of each record content RC by registering management attribute information in the record content RC.

[0040] 1.3 Third Example 5 is a diagram showing a third example of management by the content management system 10. The third example is a case where, when a stored item is digitized, the content management system 10 manages the stored item and the electronic file acquired by the digitization.

[0041] It is assumed that a user company may digitize stored items stored in the internal warehouse 210. For example, paper documents stored in the internal warehouse 210 may be digitized. Alternatively, the user company may request a management business operator to digitize stored items stored in the external warehouse 310. When stored items are digitized in this way, the content management system 10 makes it possible to manage the stored items in association with the electronic files obtained by digitization.

[0042] Assume now that user 2 is storing a "document file" in the external warehouse 310, as shown in the upper part of Fig. 5. In this case, user 2 can register and manage record content RC31 corresponding to the "document file" in database D10, as shown in the lower part of Fig. 5. User 2 can also register, as item storage information, in record content RC31 set for item content, that the storage location is the external warehouse 310.

[0043] Now, suppose that the "document file" stored in the external warehouse 310 is digitized and two electronic files, "Document1.pdf" and "Document2.pdf", are obtained. At this time, the user 2 can register the file content FC31 corresponding to "Document1.pdf" and the file content FC32 corresponding to "Document2.pdf" in the database D10 as subcontents of the record content RC31. When the digitization is performed by a management company, the registration in the database D10 may be performed by an operator 3 of the management company operating the terminal device 300.

[0044] In this way, the content management system 10 allows the user 2 to manage the stored items in association with the electronic files acquired through digitization.

[0045] 1.4 Effects As described above, the user 2 can perform various types of management on the database D10 by using the functions of the content management system 10. In particular, the user 2 can combine the above examples regarding management by the content management system 10. In this case, the database D10 in each example is the same in that it is composed of file content FC, record content RC, and sub-content subordinate to the record content RC. In other words, it is possible to centrally manage various managed objects by the database D10 while suppressing the complexity of the management situation.

[0046] Furthermore, according to the content management system 10, a managed object can be associated with one of the contents, either file content FC or record content RC. In other words, a search for a managed object in the database D10 is performed by searching for the corresponding content, regardless of the type of managed object. A search for content can be performed based on registered file attribute information or management attribute information. The file attribute information or management attribute information can be registered by the user 2 as appropriate. In this way, the content management system 10 makes it possible to ensure equal searchability for various managed objects.

[0047] 2 Displaying and processing the management screen The server 100 displays a management screen on the terminal device 200 to accept the operation of the user 2. The server 100 executes processing to provide various functions in response to the operation of the user 2 on the management screen. In the following, the display of the management screen and the processing executed by the server 100 in response to the operation of the user 2 on the management screen will be described with respect to the various functions. In the following description, the operation of the user 2 is performed via the terminal device 200, and it may be considered that the terminal device 200 transmits the operation performed by the user 2 to the server 100 as appropriate. Similarly, the operation of the worker 3 is performed via the terminal device 300, and it may be considered that the terminal device 300 transmits the operation performed by the worker 3 to the server 100 as appropriate.

[0048] 2.1 Viewing content and correcting registration information One of the functions provided by the server 100 is a function for the user 2 to view the contents registered in the database D10 and to modify the registered information (hereinafter referred to as a "view and modify function"). Fig. 6 is a diagram for explaining the process executed by the server 100 with respect to the view and modify function.

[0049] First, in step S100, the server 100 displays a list of contents registered in the database D10 (hereinafter also referred to as a "content list") on a management screen. For example, the server 100 displays the content list on a home screen when the management screen is started. Fig. 7 shows an example of the management screen on which the content list L10 is displayed.

[0050] 7 shows a management screen P100 (hereinafter simply referred to as "home screen P100") that displays a home screen. The home screen P100 includes a display area P110 that displays a content list L10. Typically, the server 100 displays the content list L10 created from the first layer of content on the home screen P100. The order of the contents displayed in the content list L10 may be changed as appropriate to the order of registration, name, or the like, in response to a request from the user 2.

[0051] The display of each content on the content list L10 includes a content name P10, an icon P11, a thumbnail image P12, and an operation button B11 for selecting various operations for the content. The display of the icon P11 corresponds to the type of content (record content RC or file content FC). By checking the icon P11, the user 2 can check whether each content is a file content FC or a record content RC. The user 2 can appropriately set the thumbnail image P12 for each content, as described later. The user 2 can visually determine the type of content by checking the thumbnail image P12. The display of the thumbnail image P12 is particularly effective for record content RC, which may correspond to a wide range of managed objects. Various operations related to the operation button B11 include making a request to the management company, downloading a registered electronic file, and the like.

[0052] Display area P110 further includes an operation button B10 for registering content. User 2 can register new content by operating operation button B10. Details of registering content by operating operation button B10 will be described below in "2.2 Registering Content."

[0053] In step S100, the server 100 may search for content in the database D10 in response to a request from the user 2. The server 100 may then display a content list L10 on a management screen as a search result. For example, the server 100 accepts input of search information for searching for content from the user 2. The server 100 then displays a content list L10 created from content that matches the input search information on the management screen. The search information may be any keyword, or may specify attribute items and attribute values ​​related to file attribute information or management attribute information. In particular, the server 100 can search for content by referring to file attribute information and management attribute information registered in each content.

[0054] Referring again to Fig. 6, after step S100, user 2 selects a piece of content that he or she wishes to view from the content list L10 displayed on the management screen (step S111).

[0055] Next, in step S112, the server 100 checks information about the content selected by the user 2. Specifically, the server 100 checks the type of the selected content (record content RC or file content FC), information registered in the selected content (management attribute information, item storage information, file attribute information, etc.), sub-contents subordinate to the selected content, etc.

[0056] After step S112, the server 100 executes a process according to the type of the selected content. The following describes the process executed by the server 100 when the selected content is record content and when the selected content is file content.

[0057] 2.1.1 When Record Content is Selected If the selected content is record content RC, the server 100 displays on the management screen (step S200) a content list L10 created by sub-contents subordinate to the selected record content RC (hereinafter simply referred to as "selected record content") and registration information related to the selected record content. Fig. 8 shows an example of the management screen P101 (hereinafter also referred to as "record content viewing screen P101") when record content RC is selected.

[0058] 8 shows a case where a record content with a content name "A0001" is selected as the record content. The record content viewing screen P101 includes a display area P111 that displays the content list L10, and a display area P121 that displays the registration information. The record content viewing screen P101 also includes a hierarchical display P21 that shows the hierarchy of the selected record content in the directory structure.

[0059] In the display area P111 shown in Fig. 8, each piece of content on the content list L10 is a sub-content subordinate to the selected record content. The display of each piece of content on the content list L10 is the same as in Fig. 7. The display area P111 further includes an operation button B10 for registering content.

[0060] The registration information displayed in the display area P121 includes management attribute information registered in the selected record content and setting information indicating the setting status of the selected record content. Furthermore, if the selected record content is set as an item content, the registration information displayed in the display area P121 includes item storage information registered in the selected record content.

[0061] FIG. 9 is a diagram showing an example of display in the display area P121. FIG. 9(A) is an example of display of managed attribute information. In the example shown in FIG. 9(A), managed attribute information with "contract number", "contractor", "contract date", and "contract product" as attribute items is displayed. "Class" specifies a set of attribute items. User 2 can switch the set of attribute items by changing the value of "class". For example, when "class" is "application form", the attribute items are "application number", "applicant", "application date", etc.

[0062] In displaying the managed attribute information, the user 2 can modify the registered managed attribute information by changing the value of each attribute item. For example, the user can modify the "contract product" from "product A" to "product B." When the user 2 modifies the managed attribute information, the server 100 updates the registration information of the selected record content to reflect the modified managed attribute information.

[0063] The display of the managed attribute information also includes an operation button B21 (first operation member) for adding new managed attribute information. The user 2 can additionally register new managed attribute information in the selected record content by operating the operation button B21. For example, when the user 2 operates the operation button B21, the server 100 accepts input of an attribute item and an attribute value as new managed attribute information. Then, the server 100 updates the registration information of the selected record content so as to add the input managed attribute information.

[0064] Fig. 9(B) is an example of the display of setting information. In the example shown in Fig. 9(B), information such as "content name", "thumbnail image", "type", and "hierarchy" is displayed. The values ​​of "content name" and "thumbnail image" indicated in the setting information correspond to the content name P10 and thumbnail image P12 displayed in the content list L10, respectively.

[0065] The display of setting information includes an operation button B22 for setting / changing the thumbnail image P12 displayed in the content list L10. The user 2 can set / change the thumbnail image P12 by operating the operation button B22. For example, when the user 2 operates the operation button B22, the server 100 accepts input of an image. Then, the server 100 sets the input image as the thumbnail image P12 of the selected record content.

[0066] The display of the setting information also includes an operation switch SW21 (third operation member) for switching whether or not to set the selected record content as the product content. The user 2 can set the selected record content as the product content by operating the operation switch SW21. When the operation switch SW21 is turned ON, the server 100 sets the selected record content as the product content.

[0067] Fig. 9(C) is an example of the display of item storage information. In the example shown in Fig. 9(C), item storage information related to items such as "management number", "storage form", "storage expiration date", "storage location", and "storage status" is displayed. The items of item storage information may be appropriately assigned depending on the environment in which this embodiment is applied.

[0068] In the display of the item storage information, the user 2 can modify the registered item storage information by changing the value of each item. When the user 2 modifies the item storage information, the server 100 updates the registration information of the selected record content to reflect the modified item storage information.

[0069] The display of the item storage information includes an operation switch SW22 for switching whether or not the item storage information registered in the base record content is inherited and registered in the selected record content. The user 2 can inherit and register the item storage information registered in the base record content in the selected record content by operating the operation switch SW22. When the operation switch SW22 is ON, the server 100 inherits and registers the item storage information registered in the base record content in the selected record content. However, the item storage information inherited and registered in the selected record content may relate to only some items. For example, in the example shown in FIG. 9(C), when the operation switch SW22 is ON, the server 100 may be configured to inherit and register the item storage information related to the "storage deadline date" to the "return deadline date", but not to inherit the item storage information related to the "management number" and the "storage type". This allows consideration of items that are not familiar to inherit and register.

[0070] The operation switch SW22 may be configured to be operable only when the selected record content is a subcontent of the product content. When the operation switch SW22 is turned on, the value related to the inherited and registered product storage information may be configured to be unchangeable.

[0071] In this way, the display area P121 displays registration information related to the selected record content. The display area P121 may be configured so that the display of each piece of information above can be switched by an operation of the user 2. For example, the display area P121 may include tabs corresponding to the display of each piece of information, and may be configured to display information according to a selected tab. However, the display area P121 may be configured not to display item storage information if the selected record content is not set as item content.

[0072] Referring again to Fig. 6, as described above, the server 100 accepts various modifications of the registered information from the user 2 on the record content viewing screen P101. When the registered information is modified by the user 2 (step S211), the server 100 updates the registered information of the selected record content to reflect the modifications (step S212).

[0073] Regarding modification of various registered information on the record content viewing screen P101, the presence or absence of modification authority may be set for each account of the user 2. Similarly, regarding the operation switches SW21 and SW22, the presence or absence of operation authority may be set for each account of the user 2.

[0074] As described above, when the selected content is record content, the server 100 displays the record content viewing screen P101 on the terminal device 200. The user 2 can confirm the contents of the selected record content and modify the registered information on the record content viewing screen P101. In particular, the user 2 can additionally register the managed attribute information while confirming the contents of the selected record content on the record content viewing screen P101. This is expected to enrich the managed attribute information as the user 2 repeatedly views the content. In turn, it is expected to configure a database D10 with high searchability.

[0075] 2.1.2 When file content is selected If the selected content is a file content FC, the server 100 displays the contents of the electronic file registered in the selected file content FC (hereinafter simply referred to as the "selected file content") and registration information related to the selected file content on the management screen (step S220). Fig. 10 shows an example of the management screen P102 (hereinafter also referred to as the "file content viewing screen P102") when the file content FC is selected.

[0076] 10 shows a case where the file content in which the electronic file "contract1.pdf" is registered is the selected file content. The file content viewing screen P102 includes a display area P132 that displays the contents of the registered electronic file, and a display area P122 that displays the registration information. The file content viewing screen P102 also includes a hierarchical display P21 that shows the hierarchy of the selected file content in the directory structure.

[0077] In the display area P132, the contents of the electronic file are displayed using a predetermined viewer. The viewer may be appropriately selected depending on the format of the electronic file. In the display area P132, the user 2 can check the contents of the electronic file registered in the selected file content.

[0078] The registration information displayed in the display region P122 includes file attribute information registered in the selected file content, and setting information indicating the setting status of the selected file content.

[0079] The display of the file attribute information in the display area P122 may be similar to the example shown in FIG. 9(A). In this case, in the above description, "management attribute information" should be read as "file attribute information" and "selected record content" as "selected file content." In other words, in the display of the file attribute information, User 2 can modify the registered file attribute information by changing the attribute value of each attribute item. User 2 can also operate operation button B21 (second operation member) to additionally register new file attribute information to the selected file content.

[0080] The display of the setting information in the display area P122 may be similar to the example shown in Fig. 9(B). However, the display of the setting information in the display area P122 does not include the operation switch SW21. In addition, in the above description, "management attribute information" may be read as "file attribute information" and "selected record content" as "selected file content."

[0081] In this way, the display area P122 displays registration information related to the selected file content. The display area P122 may be configured so that the display of each piece of information described above can be switched by the user 2's operation.

[0082] Referring again to Fig. 6, as described above, the server 100 accepts various modifications of the registered information from the user 2 on the file content viewing screen P102. When the registered information is modified by the user 2 (step S221), the server 100 updates the registered information of the selected record content to reflect the modifications (step S222).

[0083] Regarding modification of various registered information on the file content viewing screen P102, the presence or absence of modification authority may be set for each account of the user 2. Similarly, regarding the operation switches SW21 and SW22, the presence or absence of operation authority may be set for each account of the user 2.

[0084] As described above, when the selected content is file content, the server 100 displays the file content viewing screen P102 on the terminal device 200. On the file content viewing screen P102, the user 2 can check the contents of the registered electronic file and modify the registration information of the selected file content. In particular, the user 2 can additionally register file attribute information while checking the contents of the registered electronic file on the file content viewing screen P102. This is expected to enrich the file attribute information as the user 2 repeatedly views the file. In turn, it is expected to configure a database D10 with high searchability.

[0085] 2.2 Content Registration One of the functions provided by the server 100 is a function for the user 2 to register content in the database D10 (hereinafter referred to as a "content registration function"). The content registration function is provided, for example, when the user 2 operates the operation button B10 on the home screen P100 or the record content viewing screen P101. FIG. 11 is a diagram for explaining the process executed by the server 100 with respect to the content registration function.

[0086] First, in step S310, the server 100 displays a registration screen on the management screen to accept input of content to be registered. For example, the server 100 accepts input on the registration screen of the type of content to be registered, the content name, the electronic file to be registered and file attribute information, the management attribute information to be registered, the setting of the product content, an image to be displayed as the thumbnail image P12, and the like.

[0087] When the user 2 inputs content (step S311), the server 100 registers the input content in the database D10 (step S312). Here, the hierarchical level to which the content is to be registered may be determined according to the state of the management screen when the operation button B10 is operated. For example, when the operation button B10 is operated on the home screen P100, the hierarchical level to which the content is to be registered may be the first hierarchical level. In other words, in this case, the content to be registered is a content that has no subordinates. Also, when the operation button B10 is operated on the record content viewing screen P101, the hierarchical level to which the content is to be registered may be the hierarchical level of the selected record content. In other words, in this case, the content to be registered is a subcontent of the selected record content.

[0088] 2.2.1 Bulk Registration There may be a case where the user 2 wishes to register a plurality of electronic files as file content FC. In this case, registering the file content FC for each of the plurality of electronic files is a cumbersome task for the user 2. Therefore, in order to enable the batch registration of the file content FC, the server 100 may display the following registration screen in response to a request from the user 2.

[0089] 12 is a diagram showing an example of a registration screen P200 for collective registration of file contents FC. The registration screen P200 includes an input section R11 (first input section) that accepts input of one or more electronic files, and an input section R21 (second input section) that accepts input of file attribute information in a file format. For example, a CSV file or a spreadsheet file in which each attribute item and attribute value is written in a predetermined format is input to the input section R21.

[0090] On the registration screen P200, the user 2 can input a plurality of electronic files into the input section R11. The server 100 registers each of the input electronic files separately as file content FC in the database D10. The user 2 can also input file attribute information into the input section R21. When file attribute information is input into the input section R21, the server 100 further registers the input file attribute information in the respective file content FC. Note that the user 2 can also perform registration in a state where no electronic files are input into the input section R11 and file attribute information is input only into the input section R21. In this case, the server 100 registers the input file attribute information in the database D10 as file content FC.

[0091] By displaying the registration screen P200 in this way, the user 2 can register multiple electronic files as file content FC at once. This reduces the hassle of the registration work. Also, by displaying the registration screen P200 in this way, the user 2 can select and register three patterns of file content FC in which only an electronic file is registered, file content FC in which only file attribute information is registered, and file content FC in which both an electronic file and file attribute information are registered.

[0092] Similarly, the server 100 may display a registration screen that enables batch registration of record contents RC in response to a request from the user 2. For example, the server 100 may display a registration screen that includes an input section that accepts input of one or more pieces of management attribute information in a file format in response to a request from the user 2.

[0093] 2.3 Accessing Content Based on Virtual Directory Structure Consider a case where user 2 attempts to access desired content in database D10 on the management screen. The following are possible methods that user 2 can use to access the desired content. The first method is to access the desired content by selecting appropriate record content RC from content list L10, starting from the first hierarchical level, based on the directory structure of database D10. The second method is to appropriately perform a search by specifying keywords or attribute items and attribute values, and access the desired content from the search results.

[0094] On the other hand, there may be cases where User 2 frequently tries to access the same content. In such cases, User 2 may feel bothered to access the desired content using only the above methods. For example, in the first method, User 2 must perform many operations each time to access the desired content when the desired content has a deep hierarchy. Also, for example, in the second method, User 2 must perform a similar search each time to access the desired content.

[0095] As a function for dealing with the above-mentioned problem, the server 100 provides a function (hereinafter referred to as a "virtual directory search function") that enables the user 2 to access content via a virtual directory structure that can be arbitrarily set.

[0096] In the virtual directory search function, the virtual directory structure is configured by setting each hierarchy (directory) according to attribute items related to file attribute information or management attribute information. For example, one virtual directory structure is configured by setting the first hierarchy to "contract year," the second hierarchy to "contract product," and the third hierarchy to "contractor." The number of hierarchies in the virtual directory structure may be set arbitrarily.

[0097] The server 100 accepts registration of a virtual directory structure from the user 2 and manages the registered virtual directory structure. For example, the server 100 displays a registration screen for registering a virtual directory structure on the management screen in response to a request from the user 2. FIG. 13 shows an example of a registration screen P300 for registering a virtual directory structure. In the registration screen P300, the user 2 can register any virtual directory structure by setting attribute items for each layer. The "class" corresponds to a set of attribute items that can be set for each layer. The user 2 can switch the set of attribute items that can be set for each layer by changing the value of the "class". The server 100 may manage a plurality of virtual directory structures with different settings for each layer. The user 2 selects a virtual directory structure to be used in the virtual directory search function from among the plurality of registered virtual directory structures.

[0098] The virtual directory search function allows User 2 to access content via a selected virtual directory structure. An overview of the virtual directory search function will be described with reference to FIG.

[0099] In the virtual directory search function, the server 100 accepts the selection of attribute values ​​in order from the first level in the virtual directory structure. Then, the server 100 displays on the management screen a content list L10 created from the contents that match the selected attribute values.

[0100] For example, as shown in Fig. 14(A), it is assumed that file attribute information or management attribute information for three contents, content #1, content #2, and content #3, is registered in database D10. In this case, the virtual directory search function enables user 2 to access each content as follows, according to the selected virtual directory structure.

[0101] Now, assume that a virtual directory structure with the first layer being "contract year" and the second layer being "contract product" is selected. In this case, the server 100 first accepts input of the attribute value of "contract year". Next, the server 100 accepts selection of the attribute value of "contract product". Then, the server 100 displays on the management screen a content list L10 created with contents whose attribute values ​​registered for "contract year" and "contract product" match the selected attribute value. Therefore, the user 2 can access each content as shown in FIG. 13(B). For example, consider a case where the user 2 is trying to access the content #2. In this case, the user 2 first sets the "contract year" to "2023" and then sets the "contract product" to "product B".

[0102] As another example, assume that a virtual directory structure is selected in which the first layer is "contractor" and the second layer is "contract year." In this case, user 2 is able to access each content as shown in FIG. 13(C). For example, consider a case in which user 2 attempts to access content #2. In this case, user 2 first sets "contractor" to "Onebishi Saburo" and then sets "contract year" to "2023."

[0103] In this way, the virtual directory search function allows the user 2 to access content based on a virtual directory structure that can be set arbitrarily, without relying on the directory structure of the database D10, thereby reducing the hassle that the user 2 feels when trying to access the desired content.

[0104] FIG. 15 is a diagram for explaining the process executed by the server 100 regarding the virtual directory search function.

[0105] In step S400, user 2 selects a virtual directory structure to be used in the virtual directory search function.

[0106] Next, in step S410, the server 100 displays on the management screen a list of selectable attribute values ​​(hereinafter referred to as a "selection list") for each level, starting from the first level, based on the selected virtual directory structure. Fig. 16(A) shows an example of the management screen P103 (hereinafter referred to as a "virtual directory search screen P103") on which the selection list L20 is displayed.

[0107] The virtual directory search screen P103 includes a display area P113 that displays a selection list L20. The virtual directory search screen P103 also includes a virtual hierarchy display P22 that shows the hierarchy in the virtual directory structure. The display area P113 includes a display P31 of attribute items set in the current hierarchy. Each item on the selection list L20 also includes a display P32 of the corresponding attribute value. The user 2 selects an appropriate attribute value from the selection list L20.

[0108] Referring again to Fig. 15, when the user 2 selects an attribute value for each layer (step S411), the server 100 displays a content list L10 created with contents that match the selected attribute value on the management screen (step S412). Fig. 16(B) shows an example of the management screen P104 (hereinafter referred to as "virtual directory search result screen P104") in step S412.

[0109] The virtual directory search result screen P104 includes a display area P114 that displays the content list L10. The virtual directory search result screen P104 also includes a virtual hierarchy display P22. On the virtual directory search result screen P104, the display of each piece of content on the content list L10 includes an actual hierarchy display P23 that shows the hierarchy in the directory structure of the database D10. Otherwise, the display of each piece of content on the content list L10 may be the same as that in FIG.

[0110] 2.4 Request to the management company One of the functions provided by the server 100 is a function for requesting a management company to perform a predetermined operation on a stored item with respect to the item content (hereinafter, referred to as a "request function"). Fig. 17 is a diagram for explaining a process executed by the server 100 with respect to the request function.

[0111] First, in step S510, the server 100 displays on the management screen a request menu from which various requests to the management company regarding the specified item content can be selected in response to a request from the user 2. For example, the server 100 displays the request menu in response to an operation of the operation button B11 for the specified item content on the home screen P100 or the record content viewing screen P101. In this embodiment, the requests selectable on the request menu include depositing the stored item in another warehouse, ordering the stored item, discarding the stored item, and digitizing the stored item.

[0112] Depositing stored items at another warehouse, for example, is a request to deposit stored items from the internal warehouse 210 to the external warehouse 310. Ordering stored items, for example, is a request to order stored items from the external warehouse 310 to the user 2. Disposing of stored items, for example, is a request to dispose of stored items stored in the internal warehouse 210 or the external warehouse 310. Digitizing stored items, for example, is a request to digitize stored items stored in the internal warehouse 210 or the external warehouse 310.

[0113] The user 2 can select any of the above requests from the request menu. When any of the requests is selected by the user 2 (step S511), the server 100 confirms the contents of the selected request (step S512). The server 100 then notifies the worker 3 of the information on the stored item corresponding to the specified item content (typically, item storage information) and the request contents (step S513). For example, the server 100 displays a display showing the information on the stored item and the request contents on the terminal device 300. The terminal device 300 may be configured to emit a sound to notify the worker 3 of the notification when the notification is made.

[0114] After checking the notification content (step S514), the worker 3 carries out the requested content (step S515). After completing the requested content, the worker 3 operates the terminal device 300 to notify the server 100 of the completion of the request (step S516). If the requested content is digitization of the stored items, the worker 3 further transmits the electronic file obtained by digitization (hereinafter referred to as the "digitized file") to the server 100 (step S517).

[0115] If the request is for depositing the stored item other than the digitization of the stored item, the server 100 updates the item storage information of the specified item content upon receiving a notification of the completion of the request (step S520). For example, if the request is for depositing the stored item from the internal warehouse 210 to the external warehouse 310, the server 100 updates the value of the "storage location" from "internal warehouse" to "external warehouse". For example, if the request is for ordering the stored item from the user 2, the server 100 updates the "storage status" from "in storage" to "on loan". For example, if the request is for disposal of the stored item, the server 100 updates the "storage status" from "in storage" to "discarded". Alternatively, the server 100 may delete the specified item content from the database D10.

[0116] If the request is to digitize the stored item, the server 100 registers the received digitized file as file content FC in the database D10 (step S530). In particular, the server 100 registers the digitized file as subcontent subordinate to the specified item content.

[0117] As described above, the request function allows the user 2 to make various requests to the management company regarding stored items managed in the database D10. This makes it possible to realize a highly convenient content management system 10.

[0118] 3. Hardware Configuration The following describes the hardware configuration of the server 100. Fig. 18 is a diagram showing an example of the hardware configuration of the server 100. The server 100 includes a processor 110, a storage device 120, and a communication interface .

[0119] The processor 110 executes various processes. The processor 110 can be configured, for example, with a central processing unit (CPU) including an arithmetic unit and a register, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.

[0120] The storage device 120 stores various information necessary for the execution of processes by the processor 110. The storage device 120 can be configured with a recording medium such as a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD).

[0121] The communication interface 130 is an interface for connecting to the communication network 1 and communicating with devices external to the server 100. The communication interface 130 is, for example, a device for connecting to the Internet. The server 100 communicates with the terminal device 200 and the terminal device 300 via the communication interface 130.

[0122] The storage device 120 stores a computer program 121 and a database D10.

[0123] The computer program 121 is executed by the processor 110. The above-mentioned various processes by the server 100 may be realized by cooperation between the processor 110 executing the computer program 121 and the storage device 120. In particular, the content management program according to this embodiment is realized by the computer program 121 that causes the server 100 to execute the above-mentioned various processes. The computer program 121 may be recorded on a computer-readable recording medium. [Explanation of symbols]

[0124] 1. Communication Network 2. Users 10. Content Management Systems 100 Servers 121 Computer Programs 200 Terminal Equipment D10 Database RC Records Content FC File Content L10 Content List P12 Thumbnail image

Claims

1. A terminal device that accepts user operations; A server connected to the terminal device; Equipped with The server, A process of accepting input of file contents for registering an electronic file and file attribute information relating to the electronic file, or record contents for registering management attribute information relating to a desired management target, via the terminal device; A process of registering the input file content or record content in a database and managing the same; a process of registering the input file content or the record content as a sub-content subordinate to a base record content selected from the record contents registered in the database in response to a request from the user; It is configured to run Content management system.

2. 2. The content management system of claim 1, The server further comprises: a process of setting the designated record content as an item content indicating that the management target is a storage item stored in a warehouse in response to a request from the user; A process of receiving input of item storage information regarding a storage status of the stored item with respect to the item content; A process of registering the input item storage information in the designated item content and managing it; It is configured to run Content management system.

3. 3. The content management system of claim 2, The server further comprises: and executing a process of inheriting and registering a part or all of the item storage information registered in the base record content to the item content selected from the subcontents in response to a request from the user. Content management system.

4. 3. The content management system of claim 2, The server further comprises: and executing a process of requesting a predetermined business operator to deposit the stored item in another warehouse, to order the stored item, or to dispose of the stored item, in response to a request from the user regarding the designated item content. Content management system.

5. 3. The content management system of claim 2, The server further comprises: A process of requesting a predetermined business entity to digitize the stored items with respect to the designated item content in response to a request from the user; A process of acquiring a digitized file obtained by the digitization; a process of registering the electronic file in the database as the subcontent subordinate to the designated product content; It is configured to run Content management system.

6. A content management system according to any one of claims 2 to 5, The server further comprises: a process of displaying a management screen on the terminal device for receiving an operation from the user; a process of displaying a list of the file contents and the record contents registered in the database on the management screen; a process of displaying, when an operation of selecting the record content from the list is performed, a list created by the sub-content subordinate to the selected record content and the management attribute information registered in the selected record content on the management screen; a process of displaying, when an operation of selecting the file content from the list is performed, the details of the electronic file registered in the selected file content and the file attribute information registered in the selected file content on the management screen; It is configured to run Content management system.

7. 7. The content management system of claim 6, When an operation of selecting the record content from the list is performed, the server a process of displaying, on the management screen, a first operation member for adding new management attribute information to the selected record content; a process of additionally registering new managed attribute information to the selected record content when the first operating member is operated; is configured to further Content management system.

8. 7. The content management system of claim 6, When an operation of selecting the record content from the list is performed, the server a process of displaying, on the management screen, a third operation member for switching whether or not the selected record content is set as the item content; a process of displaying, when the selected record content is set as the item content, the item storage information registered in the selected record content on the management screen; The method is configured to further perform the steps of:

9. 7. The content management system of claim 6, When an operation of selecting the file content from the list is performed, the server a process of displaying, on the management screen, a second operation member for adding new file attribute information to the selected file content; a process of additionally registering new file attribute information to the selected file content when the second operating member is operated; is configured to further Content management system.

10. 7. The content management system of claim 6, the file attribute information and the management attribute information each include information on one or a plurality of attribute items; The server further comprises: A process of receiving an input of a virtual directory structure in which each hierarchical level can be set by the one or more attribute items; A process for managing the input virtual directory structure; a process of searching for the file content or the record content registered in the database based on the virtual directory structure in response to a request from the user; A process of displaying a list created from the file contents or the record contents of the search results on the management screen; It is configured to run Content management system.

11. 7. The content management system of claim 6, the server is further configured to execute a process of accepting registration of an image with respect to the designated file content or record content in response to a request from the user; The list is created such that the registered images are displayed at the positions of the corresponding file contents or record contents. Content management system.

12. A content management system according to any one of claims 1 to 5, The server further comprises: a process of displaying, in response to a request from the user, a registration screen on the terminal device, the registration screen including at least a first input unit that accepts input of one or more electronic files and a second input unit that accepts input of the file attribute information; a process of registering, in the database, one or more file contents corresponding to each of the one or more input electronic files when the one or more electronic files are input to the first input unit; a process of registering the input file attribute information in each of the one or more file contents when the file attribute information is input to the second input unit; It is configured to run Content management system.

13. A content management program for causing a computer to manage content, The content management program is A process of receiving input of file contents for registering an electronic file and file attribute information relating to the electronic file, or record contents for registering management attribute information relating to a desired management target; A process of registering the input file content or record content in a database and managing the same; registering the input file content or record content as a sub-content subordinate to a base record content selected from the record contents registered in the database in response to a request; The computer is configured to execute Content management program.

Images