JP7026410B2 - Information management system, server and user terminal - Google Patents

Description

The present invention relates to an information management technique.

Various software tools are provided for multiple users to share information. For example, by checking the schedule with a group calendar and checking the work progress with workflow software, an environment is being created in which a large number of users can easily collaborate even if they are geographically separated.

Japanese Unexamined Patent Publication No. 2016-27012

The more people involved, the larger the information and the easier it is to structure it. For example, in a product development project, various information related to research and development, material procurement, advertising, fund management, etc. is generated. In addition, research and development may include software development, and software development may include communication protocol development work.

The project leader wants to have a broad view of everything from R & D to fund management, but trying to get the full details of the information about the project is rather unproductive because of the information overload. Development engineers, on the other hand, need to know more about R & D information, but not so much about work in other areas, such as money management. Even if the members are participating in the same project, the information they want to know is not the same in terms of level and quantity.

Moreover, even if the information is needed by a certain user at a certain time, it will not be needed soon. The information is fresh. It is important to produce and share information, but it is also important to properly erase information that is no longer needed.

The present invention is an invention completed based on the above-mentioned problem recognition, and a main object thereof is to provide a technique for facilitating a user to extract necessary information from an information set.

The server in one embodiment of the present invention is connected to a plurality of user terminals via a communication network.
This server provides a user screen provider that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to the user terminal, and a user for the user screen. It is provided with an entity setting unit that creates an entity containing process progress information and a deletion setting unit that deletes the entity data from the storage medium according to the selection of the form from and the instruction to create the entity based on the selected form. ..
The deletion setting unit sets a predetermined grace period when the end setting is made in the progress information of the entity, and deletes the data of the entity from the storage medium on condition that the grace period has elapsed.

The server in another aspect of the present invention is connected to a plurality of user terminals via a communication network.
This server provides a user screen provider that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to the user terminal, and a user for the user screen. Follow the instructions for selecting a form from and creating an entity based on the selected form, in the entity settings section that creates the entity, and for the user screen to select the form or entity from the user and instruct to delete the selected form or entity. Therefore, it includes a deletion setting unit that sets a predetermined grace period for the selected form or entity.
The deletion setting unit deletes the data of the form or the entity from the storage medium on condition that the grace period has elapsed.

The user terminal in a certain aspect of the present invention is prepared in advance in a user screen display unit that displays a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form. Among the plurality of items that have been set, an item input unit that accepts the designation of the item to be activated from the user and an entity creation input unit that accepts the input of item data for the item enabled in the form are provided.
The user screen display unit hides the entity when the end is instructed in the progress information of the entity or when a predetermined grace period has elapsed from the end instruction.

The information management system in one embodiment of the present invention includes one or more user terminals and servers interconnected via a communication network.
The server is from a user screen provider that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to the user terminal, and a user for the user screen. It is provided with an entity setting unit that creates an entity including process progress information and a deletion setting unit that deletes the entity data from the storage medium according to the selection of the form and the instruction for creating the entity based on the selected form.
The user terminal has a user screen display unit that displays the user screen, an item input unit that accepts from the user the specification of the item to be activated among a plurality of items prepared in advance in the form, and an item enabled in the form. It is provided with an entity creation input unit that accepts input of item data for.
The entity setting part of the server sets the data set of the entity by accepting the input of the item data to one or more enabled items included in the form.
The deletion setting unit of the server sets a predetermined grace period when the termination setting is made for the entity, and deletes the data of the entity from the storage medium on condition that the grace period has elapsed.
The user screen display unit of the user terminal hides the entity when the end setting is made for the entity or when a predetermined grace period has elapsed from the end instruction.

According to the present invention, it becomes easy for a user to extract information necessary for himself / herself from an information set.

It is a hardware configuration diagram of an information management system. It is a functional block diagram of a server. It is a functional block diagram of a user terminal. It is a schematic diagram for demonstrating the relationship between a form and an entity. It is a screen view of a home screen. This is the form creation screen. It is a screen view of the form 1st definition screen. It is a screen view of the form 2nd definition screen. It is the first screen figure of the entity creation screen. It is a screen view of a form list screen. It is a screen diagram of the entity list screen. It is the 2nd screen figure of the entity creation screen. It is a screen view of the achievement screen. It is a flowchart which shows the processing process after the process completion of the entity. It is a screen view of a calendar screen. It is a schematic diagram which shows the correspondence relationship between a key item and an image. It is a screen view of an image preparation screen. It is a schematic diagram which shows the correspondence relationship between a tag and an image. It is a screen view of a display attribute setting screen. It is a schematic diagram for demonstrating the duplication method of an entity.

In this embodiment, the project management of a clothing maker that designs children's clothing will be described.
Generally, in a clothing manufacturer, the "chief director" creates the concept of children's clothing. At the concept stage, only the images and features of children's clothing are summarized in the form of rough sketches. A "designer" creates multiple design proposals according to the concept.

Once the design proposal is decided, "Patterner" creates a pattern by CAD (Computer-Aided Design). Next, we will actually make a prototype of children's clothing based on the pattern. The "material manager" procures prototype supplies (fabric, fasteners, etc.). While repeating trial production and procurement, check the silhouette, comfort, productivity (manufacturability), etc. The patterner also corrects the pattern as appropriate while observing the quality of the prototype.

When the prototype is completed, the clothing manufacturer places an order for mass production with an "external contractor" who operates the factory. The outside contractor creates a prototype with the fabric that will be used for the product. External vendors will consider mass productivity by actually making prototypes. As a result of reconsidering the opinions of outside vendors, it is not uncommon for designers to reconsider their designs.

By the time one child's clothing is completed, it is necessary for many people to work together to manage many processes while proceeding with the project. The "manager" who manages the project manages the complicated schedule until the children's clothes are completed. Clothing manufacturers typically run hundreds to thousands of children's clothing projects at the same time, which can be very burdensome to managers, especially.

In order for the project to proceed smoothly, it is important to improve the communication of various information related to the project. In order to improve information transmission, it is desirable to process information in a format that is easy for the recipient to understand, standardize it, and convey it. In addition, if the recipient has too much information, productivity will decrease, which may lead to human error. Therefore, it is also important to select necessary information and unnecessary information according to the recipient of the information.

In the information management system described in this embodiment, information is managed in units of "entities". An entity is a collection of information necessary for managing one process of a certain product, such as "prototype of design proposal of bag a" and "prototype of mass production of lesson bag b". Entities are created based on a standard called "form". The form defines the data structure of the entity.

One or more users are associated with the form as "members". For example, when the users P1, P2, and P3 are associated with the form F1, the entity E11 (information set) created based on the form F1 is accessible only to the users P1, P2, and P3. In other words, users other than these three users cannot know the information of the entity E11. With such an information management method, it is possible to narrow down the members for each entity (information set).
Hereinafter, the details of the information management system in this embodiment will be described.

FIG. 1 is a hardware configuration diagram of the information management system 100.
In the information management system 100, a plurality of user terminals 110a, 110b ... 104n (hereinafter, collectively referred to as "user terminal 110" when collectively referred to or not particularly distinguished) are connected to the server 200 via the Internet 102. Is connected. The user terminal 110 in this embodiment is assumed to be a smartphone. The user terminal 110 may be a general-purpose computer such as a laptop PC. The user terminal 110 and the Internet 102 are wirelessly connected.

The user terminal 110 is used by a user (employee or an outside contractor) of a clothing manufacturer. The server 200 provides the user terminal 110 with an information sharing service related to the children's clothing project. It is not necessary to install dedicated software on the user terminal 110, and the user terminal 110 can receive the service by accessing the server 200 from a web browser.

FIG. 2 is a functional block diagram of the server 200.
Each component of the server 200 includes hardware including a CPU (Central Processing Unit) and a computing unit such as various co-processors, a storage device such as a memory and a storage, and a wired or wireless communication line connecting them. , Which is stored in a storage device and realized by software that supplies processing instructions to a processor. The computer program may be composed of a device driver, an operating system, various application programs located on the upper layer thereof, and a library that provides common functions to these programs. Each block described below shows a block for each function, not a configuration for each hardware.
The same applies to the user terminal 110.

The server 200 includes a communication unit 202, a data processing unit 204, and a data storage unit 206.
The communication unit 202 is in charge of communication processing. The data storage unit 206 stores various data related to the form and the entity. The data processing unit 204 executes various processes based on the data acquired by the communication unit 202 and the data stored in the data storage unit 206. The data processing unit 204 also functions as an interface between the communication unit 202 and the data storage unit 206.

The communication unit 202 includes a transmission unit 208 and a reception unit 210.
The transmitting unit 208 transmits various data to the user terminal 110, and the receiving unit 210 receives various data from the user terminal 110. The transmission unit 208 includes an update notification unit 212. When the data included in the entity is updated, the update notification unit 212 notifies the members of this entity that the update has occurred.

The data processing unit 204 includes a user screen providing unit 214, a form setting unit 216, an entity setting unit 218, a member setting unit 220, an entity update unit 222, a corresponding registration unit 224, a search unit 226, a friend setting unit 228, and a genre setting unit 229. And the deletion setting unit 302 is included.

The user screen providing unit 214 generates various user screens and provides them to the user terminal 110. The user screen is provided as a web page. The user screen providing unit 214 includes a calendar display unit 300. The calendar display unit 300 provides a calendar screen, which is a part of the user screen, as a web page (described later in relation to FIG. 15). The form setting unit 216 creates a form according to an instruction from the user. A form ID is given to the form. The entity setting unit 218 creates an entity according to an instruction from the user. The entity is given the entity ID and the form ID of the form from which the entity is derived.

The member setting unit 220 sets a member for the form. The creator of the form associates the form ID with the user ID of the member by inviting another user as a member. The entity update unit 222 updates the data included in the entity according to the instruction from the user. Correspondence registration unit 224 associates form with form according to instruction from user. The search unit 226 searches for a form or an entity according to a search instruction from the user.

The friend setting unit 228 manages friend settings between users. The method of setting friends is the same as that of a general SNS (Social Networking Service). For example, the user P1 selects a user P2 who wants to be a friend from the users registered in the server 200, and sends a "friend request". If the user P2 "approves", the friend setting unit 228 registers the user P1 and the user P2 as "friends". The genre setting unit 229 sets the "genre" as a group of forms. Many forms can be classified as groups by genre.

FIG. 3 is a functional block diagram of the user terminal 110.
The user terminal 110 includes a user interface processing unit 114, a data processing unit 116, a communication unit 118, and a data storage unit 120.

The communication unit 118 is in charge of communication processing. The user interface processing unit 114 is in charge of processing related to the user interface, such as image display and audio output, in addition to accepting operations from the user. The data storage unit 120 stores various data. The data processing unit 116 executes various processes based on the data acquired by the communication unit 118 and the user interface processing unit 114 and the data stored in the data storage unit 120. The data processing unit 116 also functions as an interface for the user interface processing unit 114, the communication unit 118, and the data storage unit 120.

The communication unit 118 includes a transmission unit 134 that transmits various data to the server 200 and a reception unit 136 that receives data from the server 200. The input result from the user is appropriately transmitted to the server 200 by the transmission unit 134.

The user interface processing unit 114 includes an input unit 122 that accepts input from the user and an output unit 124 that outputs various information to the user.
The input unit 122 includes a form creation input unit 125, an entity creation input unit 128, a member input unit 130, a corresponding input unit 132, and a genre creation input unit 133. The form creation input unit 125 accepts the creation and update of the form. The form creation input unit 125 includes an item input unit 126. The item input unit 126 accepts the valid / invalid setting of the "item (described later)" of the form. The entity creation input unit 128 accepts the creation and update of the entity. The member input unit 130 accepts a setting for associating a member with a form. Correspondence input unit 132 accepts form and form correspondence setting. The genre creation input unit 133 accepts creation and updating of genres.

The output unit 124 includes an update notification unit 129. The update notification unit 129 notifies the user of the update of the entity on the screen.

FIG. 4 is a schematic diagram for explaining the relationship between a form and an entity.
As mentioned above, an entity is an information set, and a form is a standard (form) that defines the data structure (form) of an entity. Many items are prepared in advance for the form (hereinafter referred to as "basic item group"). Details will be described later, but when creating a form, you can define the type and amount of data of the entity by selecting and activating the item you want to use from the basic item group.

For example, when the form Fa enables the item 1, the item 2, and the item 3, the entity Ea1 created from the form Fa also includes the item 1, the item 2, and the item 3, and the data corresponding to these three items (hereinafter, the following). "Item data") is set. Further, when Form Fb enables Item 1, Item 4, Item 5, Item 6, and Item 7, the entity Eb1 created from Form Fb also includes Item 1, Item 4, Item 5, Item 6, and Item 7. Includes 5 item data. The entity Eb1 has a larger amount of data than the entity Ea1, and the item 1 and the item 4, that is, a part of the data structure is common.

In this way, an entity is created from a form (standard). You can create multiple entities from one form. In FIG. 4, three entities E11, E12, and E13 are created from the form F1. Further, one entity E21 and E22 are created from the form F2.

The entity in the present embodiment is an information set for managing the schedule of one of a large number of processes related to the production of children's clothing. Below, Form F1 corresponds to "mass production arrival schedule", entity E11 is "mass production arrival schedule of bag a", entity E12 is "mass production arrival schedule of lesson bag b", and entity E13 is "mass production arrival of lunch bag c". It is supposed to be "planned". Further, it is assumed that the form F2 corresponds to "design pattern production", the entity E21 is "design pattern production of hakama a", and the entity E22 is "design pattern production of apron d".

For example, when managing the schedule of mass production arrival schedule of children's clothing, form F1 for "mass production arrival schedule" is created. Next, in order to manage the mass production arrival schedule of hakama a, the entity E11 (mass production arrival schedule of hakama a) is created from the form F1 (mass production arrival schedule). For the lesson bag b, another entity E12 (scheduled for mass production of the lesson bag b) can be created from the same form F1. Entity E11 (planned to be mass-produced in bag a) and Entity E12 (scheduled to be mass-produced in lesson bag b) are made from the same form F1 (scheduled to be mass-produced), so the item data (contents) of the two entities are different. The data structure (item) is the same. By defining the data structure by the form, the data structure of the entity can be standardized and standardized, so that the information visibility can be improved.

As mentioned above, one or more members (users) are associated with the form. In FIG. 4, the members of Form F1 (scheduled to be mass-produced) are users P1, P2, and P3. The access authority to the entities E11, E12, and E13 derived from the form F1 (scheduled to be mass-produced) is limited to the users P1, P2, and P3.

Similarly, the members of Form F2 (design pattern production) are users P1 and P4. The access authority to the entity E21 (hakama design pattern production) and the entity E22 (apron d design pattern production) derived from the form F2 (design pattern production) is limited to the users P1 and P4.

Therefore, the users P2 and P3 can access the entities E11, E12 and E13, but cannot access the entities E21 and E22. User P1 can access all five of these entities. User P4 can access only the entities E21 and E22. User P5 cannot access any of the entities shown in FIG.

As described above, by associating a member with a form, it is possible to limit the access authority to the entity derived from the form. Therefore, it is possible to separate information that should be conveyed, information that does not need to be conveyed, and information that should not be conveyed to individual users (related persons) involved in the project. By limiting the provision of unnecessary information while enhancing information sharing, stress caused by excessive information can be reduced. In addition, setting access authority to the entity is also effective in preventing information leakage.
Hereinafter, the flow of the main processing will be described with a focus on the user screen.

FIG. 5 is a screen view of the home screen 150.
When the user accesses the server 200 from the user terminal 110, first, the user is registered by inputting the user ID (email address) and the password. When the server 200 is accessed after the user registration, the user screen providing unit 214 of the server 200 displays the home screen 150 on the user terminal 110.

The "user screen" in the present embodiment is a general term for a plurality of types of screens such as the home screen 150 provided from the server 200 to the user terminal 110. At the bottom of the user screen, a home button 152, a form button 154, a user button 156, a genre button 158, and a custom button 160 are displayed. The user can display the home screen 150 at any time by touching the home button 152. The form button 154 and the like will be described later.

The search area 162 is displayed in the center of the home screen 150. When the user inputs a search word in the search area 162, the search word is transmitted from the user terminal 110 to the server 200. The search unit 226 searches for a form or entity containing a search word. The user screen providing unit 214 displays the search result on the user terminal 110.
In the following, it is assumed that the user P1 creates the form F1.

FIG. 6 is a screen view of the form creation screen 170.
When the user P1 touches the form button 154 and then touches the new creation button (not shown) displayed on the screen, the user screen providing unit 214 causes the user terminal 110 to display the form creation screen 170. The form name area 172 is displayed in the center of the form creation screen 170. The user inputs the form name of the form F1 in the form name area 172. In FIG. 6, the form name "scheduled to be mass-produced" is input. The form name is arbitrary. Touching the cancel button 174 cancels the form creation. When the user P1 touches the save button 176, the form setting unit 216 creates a new form. The form setting unit 216 generates a form ID, and registers the form ID (form F1), the form name (scheduled to be mass-produced), and the creator (user P1) in the data storage unit 206 in association with each other.

FIG. 7 is a screen view of the form first definition screen 180.
When the form F1 (scheduled to be mass-produced) is newly created, the user screen providing unit 214 displays the form first definition screen 180. The user defines the data structure of the form F1 (scheduled to be mass-produced), that is, valid items and invalid items on the form first definition screen 180. The user P1 can also display the form first definition screen 180 by selecting the form F1 after touching the custom button 160.

By touching the name change button 182, the name of the form F1 can be changed. By touching the correspondence setting button 184, another form can be associated with the form F1.

If you touch the publish button 186, you can select open house or limited release. In the case of open to the public, access to the entity derived from Form F1 (scheduled to be mass-produced) (hereinafter, may be referred to as "entity (F1)") is not restricted without limiting the members. In this case, the entity setting unit 218 may publish the entity (F1) as a normal web page.

By touching the calendar button 304, it is possible to set whether or not to display the entity (F1) on the calendar screen. The calendar screen will be described later in relation to FIG. By touching the related image button 306, it is possible to set whether or not the image set as the item data of the entity (F1) can be used as the "related image" in another entity. Details of the related images will be described later in relation to FIGS. 16 and 17. By touching the display order button 308, the display order of the entity (F1) can be set. The display order will be described later in relation to FIG.

When the item definition button 188 is touched, an item to be activated in Form F1 (hereinafter, also referred to as "valid item") can be selected from the basic item group. Details will be described in relation to FIG. 8 below.

FIG. 8 is a screen view of the form second definition screen 190.
In the form first definition screen 180 of FIG. 7, when the item definition button 188 is touched, the user screen providing unit 214 displays the form second definition screen 190. The second definition screen 190 of the form displays a list of basic items. The user P1 selects an item required for Form F1 (scheduled to be mass-produced), that is, a valid item from the basic item group. User P1 selects on (enable) and off (disable) each item. Items that are set to ON are valid items in Form F1 (scheduled to be in stock for mass production). The item input unit 126 detects on / off of the item, the transmission unit 134 of the user terminal 110 transmits the selection result to the server 200, and the form setting unit 216 validates the form F1 (scheduled to be mass-produced) according to the selection result. Register the item.

Since multiple items are prepared in advance as a group of basic items, the user can control the quantity and quality of the information contained in the form (entity) simply by selecting a valid item from them. Since each form is based on a group of basic items, there is an advantage that the data structure of the form does not easily vary depending on the form creator. The item selection method makes it possible to realize the ease of creating a form, the degree of freedom in creating a form, and the uniformity of the data structure as a whole.

After selecting the form F1 (scheduled to be in stock for mass production), the user P1 can add a member to the form F1 by selecting the member addition button (not shown) displayed on the screen. The user who becomes a member is a user who is registered as a user in the server 200, and is a user who is registered as a "friend" with respect to the user P1 who is the creator of the form F1.

For example, after the user P1 creates the form F1 (scheduled to be in stock for mass production), when the member addition button (not shown) displayed at a predetermined position such as the right corner of the screen is touched, the friend setting unit 228 is set to the user P1's "friend". The user who is "" is selected as a member candidate. The user P1 selects a member of the form F1 from the member candidates. The member input unit 130 accepts the addition of a member, and the member setting unit 220 associates the form F1 with the member. The same applies to the deletion of members.

FIG. 9 is a first screen view of the entity creation screen 240.
After selecting the created form F1 (scheduled to be in stock for mass production), when the user touches the new creation button (not shown) displayed in the right corner of the screen, the user screen providing unit 214 is in the form F1 (scheduled to be in stock for mass production). The entity creation screen 240 for creating an entity based on is displayed. An entity (F1) is generated by inputting item data for a valid item of form F1.
In the following, it will be described that the user P1 creates the entity E11 (the mass production arrival schedule of the hakama a) based on the form F1 (the mass production arrival schedule).

The entity creation input unit 128 detects the input of item data to the entity creation screen 240. The transmission unit 134 of the user terminal 110 transmits the input item data together with the item ID to the server 200. The entity setting unit 218 of the server 200 sets the entity ID when the entity is created. The entity setting unit 218 registers each item data together with the form ID, the entity ID and the item ID.

The entity name area 242 is an area for inputting an entity name. The entity name area 242 is always a valid item, and in FIG. 9, "new hakama set arrival" is input. This entity E11 is an information set regarding the "mass production arrival schedule" of the "new hakama set (hakama a)" based on the form F1 "mass production arrival schedule".

The product number area 248 is an area for inputting a product number (see FIG. 8). The product number area 248 can be enabled / disabled. In FIG. 9, the product number “12074” corresponding to the hakama a is input. The lot area 250 is an area for inputting lots (see FIG. 6). The schedule area 246 is an area for registering the start date and the end date as the schedule of the entity E11.

The image registration area 244 is an area for registering an image. It is desirable that the image registered here is an image that symbolizes the contents of the entity E11 (scheduled for mass production of hakama), in other words, an image that makes it easy to intuitively understand "being an entity related to hakama". .. Since one entity has a plurality of image registration areas 244, it is possible to register a plurality of images for one entity.

The image registration area 244 includes an image display area 310, an image explanation area 312, and a registration button 314. The image display area 310 displays the registered image. Hereinafter, the image registered in the image display area 310 is simply referred to as a "registered image". Further, the registered image R1 of the entity E11 is described as "registered image R1 (E11)". The user P1 can describe the description about the registered image in the image explanation area 312. In the image registration area 244 in which the registered image does not exist, the registration button 314 of the image display area 310 is described as "image setting". If you touch the registration button 314 when you have not registered, a screen where you can select the image to be registered is displayed (described later in relation to FIG. 17). In the image registration area 244 in which the registered image exists, the registration button 314 of the image display area 310 is described as "clear". When the registration button 314 (clear) is touched in the image registration area 244 in which the image has been registered, the registered image in the image display area 310 is deleted.

The user P1 inputs the item data of other valid items while scrolling the entity creation screen 240. The user P1 can input / confirm all the item data of the entity E11 (scheduled for mass production of hakama a) by scrolling the entity creation screen 240. When the entity creation screen 240 shown in FIG. 9 is scrolled downward, the entity creation screen 240 described later is displayed in relation to FIG. 12.

If the user touches the delete button 252 when creating a new entity E11 (scheduled for mass production of hakama a), the entity E11 is not saved. After creating the entity E11, the user can edit the entity E11. When the user touches the delete button 252 while editing the entity E11, the delete flag of the entity E11 is turned on and the entity E11 is automatically deleted after a predetermined period of time, but the details will be described later.

If the user touches the cancel button 254 when creating a new entity E11 (scheduled for mass production of hakama a), the entity E11 is not saved. When the user touches the cancel button 254 while editing the entity E11, the entity E11 remains but the newly input item data is discarded without being registered. You can duplicate an entity by touching the duplicate button 256. Reproduction will be described later in relation to FIG. When the save button 258 is touched, the user terminal 110 sends the item data input together with the entity ID and the item ID to the server 200, and the entity setting unit 218 of the server 200 sends the entity E11 based on the form F1 to the data storage unit 206. Formally register.

FIG. 10 is a screen view of the form list screen 270.
After creating some forms or joining a form created by another user as a member, touch the form button 154 to display the list of forms. The form list screen 270 includes a created form area 272 and a participating form area 274.

In the user terminal 110 of the user P1, the form created by the user P1 (hereinafter referred to as "self-form") is displayed in a list in the creation form area 272. In the participation form area 274, among the forms created by users other than the user P1, the forms of which the user P1 is a member (hereinafter referred to as "other form") are displayed in a list. The form F1 (scheduled to be mass-produced) created by the user P1 on the form creation screen 170 of FIG. 6 is displayed as a self-form in the creation form area 272.

The form setting unit 216 of the server 200 creates a large number of forms by instructing the form creation from a large number of users. As described above, the form setting unit 216 registers the form ID, the form creator, the member, and the valid items in the data storage unit 206 in association with each other. The user screen providing unit 214 does not display the form to which the user P1 is not a member to the user terminal 110 of the user P1. User P1 cannot see forms or entities that are not relevant to him. Therefore, among the enormous amount of information stored in the data storage unit 206 of the server 200, only the information necessary for the user P1 can be selected and provided to the user P1.

The user P1 can display the calendar screen (see FIG. 15) by touching the calendar button 316.

FIG. 11 is a screen view of the entity list screen 280.
The entity list screen 280 shown in FIG. 11 is displayed when the user P1 touches the form F1 (scheduled to be in stock for mass production) on the form list screen 270 (see FIG. 10). Here, it is assumed that a large number of entities E11 and E12 have been created based on the form F1. The entity list screen 280 displays a list of entities derived from Form F1 (scheduled to be mass-produced) as thumbnails (extract images).

The thumbnail 282 is a thumbnail of the entity created on the entity creation screen 240 of FIG. 9 (mass production arrival schedule of hakama a (entity name: new hakama set arrival)). Among the plurality of item data input on the entity creation screen 240, the thumbnail 282 includes a registered image of the image display area 310, an entity name area 242, a schedule area 246, a product number area 248, and a part of the progress status "unprocessed". Only the item data of is displayed. By referring to the entity list screen 280, the user P1 can collectively confirm the schedule, progress status, and the like of the entity related to the form F1 (scheduled to be received in mass production).

When the user P1 touches the thumbnail 282 on the entity list screen 280, the item data group of the entity E11 (scheduled for mass production of hakama a) is displayed in detail in the same display format as shown on the entity creation screen 240.

The user screen providing unit 214 displays a plurality of entities (F1) in chronological order on the entity list screen 280 shown in FIG. User P1 can also sort the entities (F1) in order of product number instead of order of date. The display order change of the thumbnail 282 will be described later in relation to FIG.

When the user P1 selects the entity E11 (scheduled for mass production of hakama) on the entity list screen 280, the entity browsing screen (not shown) of the entity E11 is displayed. On the entity browsing screen, all item data of entity E11 can be confirmed.

Some items in the basic item group are preset as "key items". In the present embodiment, the item "product number" is a key item (see the product number area 248 in FIG. 9).

FIG. 12 is a second screen view of the entity creation screen 240.
Even after the entity E11 is created, when the user P1 touches the edit button (not shown) displayed in the right corner of the screen on the browsing screen of the entity E11, the user screen providing unit 214 uses the entity creation screen to edit the entity E11. 240 can be displayed.

As described above, the entity creation screen 240 includes a plurality of image registration areas 244. In addition to the items described in relation to FIG. 9, the entity creation screen 240 includes a man-hour area 326 showing the planned man-hours required for the work and a progress area 324 showing the progress information of the work.

The progress area 324 includes an unprocessed button 318, a processing button 320, and a completion button 322. The unprocessed button 318 is highlighted when the entity E11 (scheduled for mass production of hakama a) is created. When the start date and time of the entity E11 (see FIG. 9) is reached, the user screen providing unit 214 highlights the processing button 320. Alternatively, when any member of the entity E11 touches the processing button 320, the user screen providing unit 214 highlights the processing button 320. When the member of the entity E11 completes the process of the entity E11 (scheduled for mass production of hakama a), this user touches the completion button 322. At this time, the user screen providing unit 214 highlights the completion button 322.

FIG. 13 is a screen view of the achievement screen 330.
When the user P2 who is a member of the entity E11 touches the completion button 322 on the entity creation screen 240, the transmission unit 134 of the user terminal 110 transmits a completion notification to the server 200 together with the user ID and the entity ID of the user P2. The user screen providing unit 214 of the server 200 causes the user terminal 110 of the user P2 (hereinafter, referred to as “user terminal 110 (P2)”) to display the achievement screen 330. In addition, the update notification unit 212 also notifies the other members, users P1 and P3 (see FIG. 4), of the completion of the entity E11 (scheduled for mass production of hakama a).

On the achievement screen 330, an image praising that the user P2 has completed the entity E11 (scheduled to receive mass production of hakama a) is displayed, such as "NICE! MISSION COMPANY". The user screen providing unit 214 displays a moving image in which the confetti 332 dances on the achievement screen 330.

FIG. 14 is a flowchart showing a processing process after the process of the entity is completed.
Here, the processing process of the server 200 when the user P2 completes the entity E11 (scheduled for mass production of hakama a) will be described. First, when the user P2 touches the completion button 322 on the entity creation screen 240 of the entity E11, the transmission unit 134 of the user terminal 110 (P2) transmits a completion notification to the server 200 together with the user ID of the user P2. The user screen providing unit 214 of the server 200 causes the user terminal 110 (P2) to display the achievement screen 330 (S10).

Next, the entity update unit 222 identifies the users P1, P2, and P3 that are members of the entity E11 (scheduled for mass production of hakama), and the update notification unit 212 is a user P1 other than the user P2 who is the work completion person. An update notification is transmitted to P3 together with the user ID and entity ID of the user P2 (S12). Upon receiving this update notification, the user terminal 110 (P1) and the user terminal 110 (P3) recognize that the entity E11 (scheduled for mass production of hakama a) has been completed by the user P2. The user terminal 110 (P1), the user terminal 110 (P2), and the user terminal 110 (P3) hide the entity E11.

Next, the deletion setting unit 302 of the server 200 sets the “deletion flag” associated with the entity E11 in advance to on (S14). Further, the deletion setting unit 302 sets a "grace period" in the entity E11 (S16). In other words, turning on the delete flag sets the grace period.

The length of the grace period may be a fixed value or may be adjusted by the user. The length of the grace period may be changed depending on the user attribute, for example, whether it is a paid member or a free member. When the user P2 who has completed the work is a paid member of the information management system 100, the deletion setting unit 302 sets the grace period as 3 weeks, and when the user P2 is a free member, the grace period is set as 3 days, which is shorter than that. You may. During the grace period, the entity E11 (scheduled for mass production of hakama a) is hidden, but the data is backed up on the server 200. After the grace period has elapsed, the deletion setting unit 302 completely deletes the item data and the like related to the entity E11 from the data storage unit 206.

The deletion setting unit 302 sets the longest grace period as the grace period of the entity E11 among the three types of grace periods based on the user attributes of the users P1, P2, and P3 (members of the entity E11), not the person who completed the work. You may. For example, assume that user P1 is a paid member and users P2 and P3 are free members. In this case, even if it is the free member user P3 who completed the entity E11, the deletion setting unit 302 may set the grace period as 3 weeks according to the paid member attribute of the user P1. Since the server 200 collectively manages the data of a large number of entities, the deletion setting unit 302 may periodically delete all the entities whose grace period has expired by batch processing.

The user can also revive the entity E11 (scheduled for mass production of hakama) by inputting the revival instruction. For example, suppose user P2 completes entity E11. At this time, in the server 200, the deletion flag of the entity E11 is turned on, but the data of the entity E11 still remains in the data storage unit 206. The entity E11 (scheduled for mass production of hakama a) is hidden in the user terminal 110 which is a member of the entity E11. Here, it is assumed that the user P1 touches the grace button (not shown). At this time, the user terminal 110 transmits a grace confirmation request including the user ID to the server 200. When the grace confirmation request is received, the user screen providing unit 214 of the server 200 transmits to the user terminal 110 a list of the entities of which the user P1 is a member and the deletion flag is turned on.

Next, the user P1 selects an entity to be revived from this list and turns on the revival button (not shown). Here, it is assumed that the entity E11 (scheduled for mass production of hakama a) is selected as the revival target. The user terminal 110 (P1) transmits a resurrection request to the server 200 together with the entity ID of the entity E11 to be resurrected. The deletion setting unit 302 of the server 200 turns off the deletion flag of the entity E11. As a result, the entity E11 is provided again to the users P1, P2, P3. In addition, the deletion setting unit 302 resets the grace period when the deletion flag is turned off.

In this way, when the entity E11 (scheduled for mass production of hakama a) is completed, the entity E11 is hidden on the user terminal 110, and the data is also deleted. In addition to this, the entity can also be deleted when the user touches the delete button 252 on the entity creation screen 240. For example, suppose that the entity E12 (scheduled for mass production of the lesson bag b) is created and registered in the server 200. After that, it is assumed that the user P1 deletes the entity E12. In this case, the deletion instruction is transmitted from the user terminal 110 to the server 200 together with the entity ID of the entity E12. Upon receiving the deletion instruction, the deletion setting unit 302 turns on the deletion flag of the entity E12 and sets the grace period. After the grace period has elapsed, the deletion setting unit 302 deletes the data of the entity E12 from the data storage unit 206.

During the grace period, the user can touch the grace button and then turn on the resurrection button to revive the deleted entity. At this time, the deletion setting unit 302 turns off the deletion flag and resets the grace period.

FIG. 15 is a screen view of the calendar screen 340.
When the user P1 selects the calendar button 316 on the form list screen 270 (FIG. 10), the transmission unit 134 of the user terminal 110 transmits a calendar request to the server 200 together with the user ID. The calendar display unit 300 of the server 200 transmits the calendar screen 340 to the user terminal 110 (P1).

The calendar display unit 300 displays a plurality of entities of which the user P1 is a member on the calendar screen 340 in the form of a calendar based on the start time of the entity. All the entities derived from the self-form created by the user P1 itself are initially set to be displayed. When the user P1 selects the form F1 (self-form), the form first definition screen 180 is displayed, and the calendar button 304 is set to off, the entity (F1) is not displayed on the calendar screen 340.

An entity created by a user other than the user P1 and derived from another form in which the user P1 participates as a member is initially set so as not to be displayed. Even in the case of another person's form, by changing the calendar button 304 to the on setting on the form first definition screen 180, the entity derived from the other person's form can be displayed on the calendar screen 340.

Therefore, on the calendar screen 340, among the entities of which the user P1 is a member, only the entities for which the calendar display is set to be turned on are listed as a calendar. The server 200 manages the on / off setting of the calendar display for each form and each user. Therefore, the entity displayed on the calendar screen 340 differs depending on the user.

The calendar display unit 300 also shows the progress status (unprocessed, processed, completed) of the entity. The completed entity is set to turn on the deletion flag as described above, but it can be confirmed on the calendar screen 340 during the grace period.

The user can collectively check the schedules of the entities related to him / her on the calendar screen 340. By setting the calendar display on / off for the form, the user can narrow down the calendar display target entities from the entities of which he / she is a member.

FIG. 16 is a schematic diagram showing the correspondence between key items and images.
An entity contains multiple items. As described above, the item "product number" is a "key item". It is assumed that the entities E11, E21, and E32 shown in FIG. 16 are all "part number: 12074". Hereinafter, the entity including "X" as the item data as the key item "product number" is expressed as "entity (KEY: X)". That is, all of these three entities E11, E21, and E32 are entities (KEY: 12074). The forms from which the entities E11, E21, E32 are derived do not have to be the same.

In the entity E11, the image R1 is selected as the registered image. In the entity E21, the images R2 and R4 are selected as the registered images. Further, the images R1, R2, and R6 are selected as registered images for the entity E32. Therefore, the registered images used in the three entities E11, E21, and E32 are four types of images R1, R2, R4, and R6.

FIG. 17 is a screen view of the image preparation screen 350.
Here, the user P1 newly creates a new entity E41 in which "12074" is set as the "product number", and touches the registration button 314 for image registration on the entity creation screen 240 of the entity E41 (KEY: 12047). Suppose you did. The user terminal 110 transmits the item data "12074" of the entity ID and the key item to the server 200. The user screen providing unit 214 causes the image preparation screen 350 to be displayed on the user terminal 110 of the user P1.

The image preparation screen 350 includes a related image area 352 and a library area 354. The related image area 352 is an area for selecting a registered image from the related images. As described above, there are four types of registered images used in the entity (KEY: 12047). The search unit 226 searches for the existing entity (KEY: 12047) and detects that there are four registered images used in the three entities E11, E21, and E32. According to this, the user screen providing unit 214 adds the number "4" to the related image area 352.

When the user P1 touches the related image area 352, the related image selection screen (not shown) is displayed. The user screen providing unit 214 displays the four registered images R1, R2, R4, and R6 detected on the related image selection screen in parallel. The user can set the registered image of the entity E41 by selecting any image from the related image selection screen. The selection result is transmitted from the user terminal 110 to the server 200.

When the related image button 306 is set to off on the form first definition screen 180 after selecting the form, the registered image used in the entity derived from the form is used when creating / editing another entity. It cannot be used as a related image. For example, it is assumed that the related image is set to off for the form F1. In this case, the image R1 used in the entity E11 derived from the form F1 is excluded from the target of the related image. Therefore, the related images that can be used when the user P1 creates the entity E41 (KEY: 12047) are three types of images R2, R3, and R6.

The library area 354 is an area for selecting an image (hereinafter, referred to as “prepared image”) prepared in advance in the server 200. A "tag" is associated with the prepared image in advance. For example, since the tag "feeling" is associated with two types of preparation images, the number "2" is added to the tag "feeling" in the library area 354. When the user P1 selects any tag in the library area 354, the preparation image selection screen (not shown) is displayed. The user can set the registered image of the entity E41 by selecting any of the prepared images from the prepared image selection screen. The relationship between the tag and the prepared image will be described later.

When the user P1 touches the camera button 356, the input unit 122 of the user terminal 110 activates the camera built in the user terminal 110. The user P1 can take an image with the camera of the user terminal 110 and use it as a registered image. For example, the user P1 may set an image of a product as a registered image. When the user P1 touches the local image button 358, the registered image can be selected from the images saved by the user terminal 110.

FIG. 18 is a schematic diagram showing the correspondence between the tag and the image.
The tag is identified in advance by the tag ID. Further, the prepared image is identified by the image ID. In FIG. 18, the tags T1 are associated with the prepared images U1 and U2. Preparation images U2 and U3 are associated with the tag T2. Preparation images U4 and U5 are associated with the tag T3. In this way, the prepared image is associated with one or more tags in advance.

When the user P1 selects the tag T1 (eg, "feeling"), the preparation image selection screen in which the preparation images U1 and U2 can be selected is displayed. Similarly, when the tag T2 is selected, the preparation image selection screen in which the preparation images U2 and U3 can be selected is displayed.

FIG. 19 is a screen view of the display attribute setting screen 360.
After the user P1 selects the form F1, when the form first definition screen 180 (FIG. 7) is displayed and the display order button 308 is touched, the user screen providing unit 214 displays the display attribute setting screen 360 on the user terminal 110 (P1). ). The display attribute setting screen 360 is a screen for setting the display order of the entities on the entity list screen 280 (FIG. 11). The user selects a "date" or a "product number" in the item selection area 362. After selecting, by touching the cancel button 366, the display order regarding the form F1 is set. Touch the save button 364 to cancel the setting.

It is assumed that the user P1 selects "date" as the display order of the form F1. In this case, when the user screen providing unit 214 displays the entity list screen 280 of the form F1, the entities (F1) are displayed side by side in chronological order. Similarly, when the user P1 selects the display order "product number", the user screen providing unit 214 displays the entities (F1) in the order of the product numbers. In this way, by selecting the item that serves as the reference of the display order as the display attribute, the user P1 can confirm the entity (F1) in order from the oldest start date and time, and the entity (F1) having the same product number. You can also check the contents of.

FIG. 20 is a schematic diagram for explaining a method of replicating an entity.
Here, it is described that the entity EX generated from the form FX is duplicated to generate the entity EY. However, the entity EY is based on a different form FY than the form FX.

It is assumed that the valid items of Form FX are items 1, 2, and 4. It is assumed that the valid items of the form FY are items 1, 3 and 4. That is, the items that are commonly valid in the forms FX and FY are items 1 and 4. Let the item data of the items 1, 2, and 4 of the entity EX (FX) be D1, D2, and D3, respectively.

It is assumed that the user P1 touches the duplicate button 256 on the entity creation screen 240 of the entity EX (FX) (see FIGS. 9 and 12). At this time, the user screen providing unit 214 displays a screen for selecting a copy destination form in the same user interface as the form list screen 270 (see FIG. 10). It is assumed that the user P1 selects the form FY as the copy destination form.

At this time, the form setting unit 216 automatically sets the item data D1 (item 1) and the item data D3 (item 4) of the entity EX (duplicate source) to the items 1 and 4 of the entity EY (duplicate destination). .. On the other hand, the item 2 of the entity EX is not enabled in the entity EY. Therefore, the item data D2 (item 2) of the entity EX (duplicate source) is not set in the entity EY (duplicate destination). Further, the item 3 of the entity EY (duplicate destination) is not enabled in the entity EX (duplicate source). In this case, the form setting unit 216 does not set the item data in the item 3 of the entity EY (duplicate destination). The user P1 needs to manually input the item data in the item 3 of the entity EY.

[Summary]
The information management system 100 has been described above based on the embodiment.
According to the information management system 100, a user can create a plurality of entities by using one form as a "standard (form)". Information productivity is high because the entity is created from the form. Multiple items (basic item group) are prepared in advance in the form, and the user can easily define the data structure of the form by selecting a valid item from them. Since each form is based on the basic item group, it is possible to make multiple forms uniform. The form is customized from the basic items, and the entity as a separate information set is produced from the form.

The type and number of valid fields determines the quality and quantity of information in the entity. For example, the form (scheduled mass arrival (overall)) includes the minimum valid items such as product number and schedule, and the form (scheduled mass arrival (site)) includes the price, return rate, and display shelves to be secured at the time of arrival. Items such as the location of the item should be enabled in detail. In this case, the manager may confirm the entity derived from the form (mass production arrival schedule (overall)), and the site staff may confirm the entity derived from the form (mass production arrival schedule (details)). In this way, the amount of information required for each user can be adjusted based on the job title and position.

When the completion is instructed in the progress information of the entity, the server 200 turns on the deletion flag of the entity, sets the grace period, and automatically deletes the data of the entity. When a huge number of entities are generated, the amount of work to delete the entity is also huge. By automatically deleting the entity, it is possible to reduce the workload associated with deleting the entity and efficiently reduce the information that the user needs to know. In addition, deleting unnecessary information also contributes to the efficient use of the storage medium of the server 200. Automatic deletion of entities is also effective in preventing information leaks that were necessary in the past but are no longer necessary.

In addition, by providing a grace period, the data of the entity can be saved for a while even if the entity is no longer needed. Therefore, even if the entity is accidentally deleted, the data of the entity can be restored within the grace period, which can give the user a sense of security.

The calendar screen 340 allows the user to check the entities related to him / her as a calendar. However, when there are many entities, it may be difficult to see the calendar screen 340. Some entities want to be well-understood as a party, while others want to be roughly monitored as an outsider. In the present embodiment, by setting whether or not to display the calendar on the form, it is possible to narrow down the entities to be displayed on the calendar screen 340.

In the present embodiment, when the registered image is selected, the registered image of the existing entity common in the key item "product number" is presented as a selection candidate. For example, if the registered images are common to various entities related to "Hakama", when browsing the entities on the entity list screen 280 or the like, it becomes easy to intuitively understand which product number the entity is related to.

It is assumed that the user P1 generates the entity E11 (scheduled for mass production of hakama a) (KEY: 12074) and selects the image R1 as the registered image. When another user P2 generates the entity E21 (design pattern production of hakama a) (KEY: 12074) having the same product number, the image R1 is presented as a selection candidate. If the user P2 selects the image R1 as it is, the "image R1" is fixed as an image symbolizing the "hakama" of the product number "12074". When the user P1 creates the entity E11, the user P1 does not need to perform another operation for associating the product number “12074” with the image R1. By allowing each user to freely select a registered image and showing the registered image already selected by another user as a candidate, it is possible to naturally associate the product number with the image.

In this embodiment, the tag and the prepared image are associated with each other in advance. By selecting a tag, the user can select a registered image from the preparation images corresponding to the tag. Image management using tags makes it easier for users to select an image that suits their image even when there are a large number of images. Further, when a new image is acquired by the built-in camera of the user terminal 110 or the like, a tag may be set for this image and registered in the server 200. According to such a control method, by collecting images from a large number of users in the server 200 and associating them with tags, it becomes easy to manage these images as shared assets of the information management system 100.

By setting the display order button 308 of the form, the display order of the entities can be freely changed. In this embodiment, "date" and "product number" are exemplified, but the display order may be changed based on other items. By changing the display order of the thumbnail 282 (FIG. 11) on the entity list screen 280, the display size, the display color, the frame color of the thumbnail 282, etc., the entity list is set according to the display attribute set by the display order button 308. The display method of the screen 280 may be set. For example, it is assumed that the "project number" can be set on the display attribute setting screen 360. When the user selects "project number", the background color of the entity list screen 280 may be color-coded for each project. According to such a control method, when the user refers to a large number of entities on the entity list screen 280, it becomes easy to collectively confirm the processes for each project.

In the present embodiment, another entity EY based on the form FY can be duplicated from the entity EX based on the form FX. For example, when there is an entity EX related to design confirmation of the child shoes c, it may be desired to newly create an entity EY related to the procurement of prototype materials for the children's shoes c. At this time, the entity EY (prototype material procurement for children's shoes c) may be newly generated based on the form FY (prototype material procurement), but the entity EX (confirmation of the design of the children's shoes c) and the entity EY (children's shoes c) may be newly generated. It is thought that many of the item data of (Prototype material procurement) are likely to be the same. In the present embodiment, the entity EY is created after duplicating the item data for the valid items common to both the entity EX and the entity EY. Therefore, the input load of the item data when creating a new entity can be reduced, and the information productivity is improved. In addition, automatic duplication of item data is also effective in reducing input errors in item data.

After the creation by duplicating the entity EY (procurement of the prototype material of the children's shoes c), the user may freely change the item data initialized in the entity EY. It is also possible to duplicate another entity based on the same form FX (design confirmation) from the entity EX (design confirmation of the children's shoes c), for example, the entity (design confirmation of the boots d).

In particular, if the related image sharing function described in relation to FIGS. 16 and 17 and the entity duplication function described in relation to FIG. 20 are combined, it becomes easier to unify the registered images for each product or project. .. For example, suppose that the image R6 is used as a registration image of the entity EX for the "children's shoes c", and various entities related to the "children's shoes c" are generated using the entity EX (design confirmation of the children's shoes c) as a duplication source. In this case, since the image R6 is duplicated as a registered image even in the newly generated entity of "children's shoes c", it becomes easy to standardize and unify the registered images for each product or project.

When the process defined in the entity is completed, the user screen providing unit 214 displays the achievement screen 330. The achievement screen 330 can enhance the sense of accomplishment when the person who has completed the work finishes the work. The transmission unit 208 of the server 200 may transmit a voice message to the user terminal 110 when displaying the achievement screen 330, and the output unit 124 of the user terminal 110 may read the voice message aloud.

Designers, fashion designers, and sales people can easily recognize the achievement of their work. On the other hand, there are some occupations, such as accounting and material procurement, where it is difficult for others to recognize the achievement of the work. By displaying the achievement screen 330 each time the process defined by the entity is completed, it becomes easier to enjoy the sense of accomplishment of the work even in a back office-like occupation.

A plurality of types of achievement screens 330 may be prepared in advance. The user screen providing unit 214 may randomly display the achievement screen 330 to be displayed from the plurality of achievement screens 330. A plurality of achievement screens 330 may be prepared for each form. In this case, the user screen providing unit 214 may display the achievement screen 330 associated with the form of the achieved entity on the user terminal 110. Alternatively, a boss such as a manager or a chief director may create and register an original achievement screen 330 in advance in order to aim for the achievement of his subordinates. According to such a control method, the boss can aim at the subordinates through the achievement screen 330 when the work is accomplished, which is considered to contribute to the improvement of the morale of the organization.

The present invention is not limited to the above-described embodiment or modification, and the components can be modified and embodied within a range that does not deviate from the gist. Various inventions may be formed by appropriately combining a plurality of components disclosed in the above-described embodiments and modifications. In addition, some components may be deleted from all the components shown in the above embodiments and modifications.

[Modification example]
In this embodiment, the schedule management of the project related to the design of children's clothing has been described. Not limited to children's clothing, the information management system 100 can be widely applied to situations such as software development, product promotion, planning of sporting events, etc., which are premised on information sharing by a plurality of users.

In the present embodiment, when the work defined in the entity is completed, the deletion setting unit 302 turns on the deletion flag, sets the grace period, and deletes the data of the entity after the grace period elapses. The length of this grace period is arbitrary and may be zero.

When the entity is completed, the deletion setting unit 302 may move the data of the completed entity to the "grace folder". Further, when the grace confirmation request is received from the user terminal 110, the transmission unit 208 of the server 200 may notify the user terminal 110 of the list of the entities in the grace folder. When the user of the user terminal 110 selects the entity to be resurrected from the list of entities, the user terminal 110 sends a resurrection request to the server 200 together with the entity ID. The deletion setting unit 302 of the server 200 restores the data of the entity requested to be restored from the grace folder and turns off the deletion flag.

In the present embodiment, it has been described that the entity is deleted, but the form may be deleted. After selecting the form to be deleted on the form list screen 270, the form may be deleted by touching the delete button (not shown). In this case, the transmission unit 134 of the user terminal 110 transmits a deletion instruction to the server 200 together with the form ID to be deleted. The form setting unit 216 of the server 200 turns on the deletion flag associated with the form and sets the grace period. After the grace period has elapsed, the deletion setting unit 302 may delete the form and the entities derived from this form together.

In the present embodiment, it has been described that the form 1 definition screen 180 is displayed for the form F1 and the calendar button 304 is set to set whether or not all the entities derived from the form F1 can be displayed on the calendar screen 340. As a modification, it is possible to set whether or not to display on the calendar screen 340 for each entity instead of each form.

As described above, it is also possible to associate a plurality of registered images with one entity. When displaying an entity as a thumbnail 282 on the entity list screen 280, the user screen providing unit 214 may rotate and display a plurality of registered images at regular time intervals. Alternatively, the user screen providing unit 214 may display the first registered image among the plurality of registered images on the thumbnail 282 as a representative image.

In the present embodiment, when the image is registered in the entity (KEY: X), the registered image of the existing entity (KEY: X) is selected as the related image. As a modification, item data other than the image may be presented as a selection candidate. For example, texts such as explanatory texts, music, videos, and the like may be presented as selection candidates as related data.

For example, suppose that text data is registered in item 1 of the entity EA (KEY: X). It is assumed that the text data DB is already registered in item 1 of another entity EB (KEY: X). At this time, the entity setting unit 218 may present the text data DB as a selection candidate when inputting data to the item 1 of the entity EA (KEY: X).

In the present embodiment, a related image or the like is presented as a selection candidate, and the user is allowed to select a registered image. As a modification, the entity setting unit 218 may automatically set the item data. For example, suppose that data is registered in item 1 of the entity EA (KEY: X). It is assumed that the data DB is already registered in item 1 of another entity EB (KEY: X). Further, it is assumed that there is no entity (KEY: X) other than the entity EB (KEY: X). In this case, the entity setting unit 218 may automatically set the data DB in the item 1 of the entity EA (KEY: X).

Further, it is assumed that the data is registered in the item 1 of the entity EA (KEY: X). It is assumed that the most data DC is set in the item 1 in the existing plurality of entities (KEY: X). In this case, the entity setting unit 218 may automatically set the data DC in the item 1 of the entity EA (KEY: X).

There may be multiple key items. For example, suppose that two key items Q1 and Q2 are set. At the time of creating the entity E1, the user screen providing unit 214 presents the registered image of the entity E2 and E3 as a related image when the entity E2 and E3 whose key data of each of the key items Q1 and Q2 completely match exists. May be good. Further, the registered image of the entity E4 that matches only one of the key items Q1 and Q2 may be presented as a related image, or may be excluded from the candidates when there is an incomplete match. The same applies to item data other than images.

In the present embodiment, it has been described that the length of the grace period is set according to the user attribute. The user attributes referred to here are male and female users, users within a predetermined number of days (new users) and users with a predetermined number of days or more (long-term users), and age. , Job title, etc., as long as it is information that can categorize the user.

The user screen providing unit 214 may change the achievement screen 330 according to the number of achievements. For example, different achievement screens 330 may be prepared for each of the number of completions of the entity within 5 times, 6 to 10 times, and 10 times or more per month. The user can see the more rare achievement screen 330 by completing the work defined by the entity. According to such a control method, various achievement screens 330 can be enjoyed by efficiently advancing the work, which is considered to be effective in increasing the motivation of the user to work.

The server 200 may include an achievement count detection unit (not shown) that counts the achievement count for each user. Depending on the number of achievements, the operator of the information management system 100 may give various benefits to the user (employee). For example, free company meals, increased bonuses, and paid grants can be considered. By quantifying the hard work of employees by the number of achievements, it becomes easier to realize management that "rewards according to the results" even in occupations where it is difficult to recognize the results.

The entity setting unit 218 of the server 200 may propose to the entity creator to delete the entity with less access. For example, when the entity E35 has not been edited or viewed for one year or more, the entity setting unit 218 may send a deletion proposal to the user who created the entity E35. When the user agrees to delete, the deletion setting unit 302 turns on the deletion flag of this entity E35. According to such a control method, it becomes easy to prevent unnecessary information from being accumulated by rationally deleting unnecessary entities even after a large number of entities are created.

The form setting unit 216 may propose to delete the form having no entity. The entity setting unit 218 may propose to delete the entity related to the old schedule, for example, the entity related to the schedule one year or more ago.

In this embodiment, the description is based on the premise that the server 200 exists. This is premised on sharing information by a plurality of user terminals 110. A part of the present invention can be applied to personal information management as well as group information. For example, functions such as creating an entity based on a form and setting correspondence of a form may be implemented in the user terminal 110, and the user's schedule and memorandum may be managed for each entity only by the user terminal 110.

100 Information management system, 102 Internet, 110 User terminal, 114 User interface processing unit, 116 Data processing unit, 118 Communication unit, 120 Data storage unit, 122 Input unit, 124 Output unit, 125 Form creation input unit, 126 Item input unit , 128 Entity creation input unit, 129 update notification unit, 130 member input unit, 132 compatible input unit, 133 genre creation input unit, 134 transmitter unit, 136 receiver unit, 150 home screen, 152 home button, 154 form button, 156 user Button, 158 genre button, 160 custom button, 162 search area, 170 form creation screen, 172 form name area, 174 cancel button, 176 save button, 180 form first definition screen, 182 name change button, 184 compatible setting button, 186 Publish button, 188 item definition button, 190 form second definition screen, 200 server, 202 communication unit, 204 data processing unit, 206 data storage unit, 208 transmitter unit, 210 receiver unit, 212 update notification unit, 214 user screen provider unit , 216 form setting part, 218 entity setting part, 220 member setting part, 222 entity update part, 224 correspondence registration part, 226 search part, 228 friend setting part, 229 genre setting part, 240 entity creation screen, 242 entity name area, 244 Image registration area, 246 Schedule area, 248 Part number area, 250 lot area, 252 Delete button, 254 Cancel button, 256 Duplicate button, 258 Save button, 270 Form list screen, 272 Create form area, 274 Participation form area, 280 Entity List screen, 282 thumbnail, 300 calendar display, 302 deletion setting, 304 calendar button, 306 related image button, 308 display order button, 310 image display area, 312 image description area, 314 registration button, 316 calendar button, 318 not yet Processing button, 320 Processing button, 322 Completion button, 324 Progress area, 326 Effort area, 330 Achievement screen, 332 Confetti, 340 calendar screen, 350 image preparation screen, 352 related image area, 354 library area, 356 camera button, 358 local image button, 360 display attribute setting screen, 362 item selection area, 364 save button, 366 cancel button

Claims (16)

Connected to multiple user terminals via a communication network,
A user screen providing unit that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to a user terminal.
An entity setting unit that creates an entity including process progress information according to the user's selection of a form for the user screen and the instruction to create an entity based on the selected form.
It is equipped with a deletion setting unit that deletes the data of the entity from the storage medium.
The deletion setting unit sets a grace period when the end setting is made in the progress information of the entity, deletes the data of the entity from the storage medium, and sets the end, on condition that the grace period has elapsed. A server characterized in that the length of the grace period is set according to the attributes of the user. Users are categorized as either paid or free members,
The server according to claim 1, wherein the deletion setting unit sets the length of the grace period according to whether the user who has been set to terminate is a paid member or a free member. Further equipped with a form setting unit for creating a form according to a form creation instruction from the user on the user screen.
The user screen providing unit includes a calendar display unit that refers to progress information of an entity and displays a calendar screen indicating a scheduled date and time of one or more entities.
The form setting unit sets whether or not to display the calendar of the form or entity according to the specification from the user.
Claim 1 is characterized in that the calendar display unit displays an entity on a calendar screen, provided that it is an entity generated from a form set to be calendar displayable or an entity set to be calendar displayable. The server described in. The entity setting unit sets the data set of the entity by accepting the input of the item data to one or more items included in the form.
The user screen providing unit moves from the user to the first item in the first entity when the same item data is set in the predetermined key item in the first entity and the key item in the second entity. When the input of the item data of the above item is accepted, the item data of the first item in the second entity is displayed on the user screen as a candidate for the item data of the first item in the first entity. The server according to claim 1. When the user screen providing unit receives an image input to the first item in the first entity, the user screen providing unit uses the image of the first item in the second entity as the first image in the first entity. The server according to claim 4, wherein the server is displayed on the user screen as an input candidate for an item. When receiving the input of the item data to the first item in the first entity designated by the user, the user screen providing unit uses the same item data as the item data of the key item in the first entity as a key. When the second entity and the third entity set in the item exist, both the item data of the first item in the second entity and the item data of the first item in the third entity. The server according to claim 4 or 5, wherein one of them is displayed on the user screen as a candidate for the item data of the first item in the first entity. It further includes an entity update unit that updates the item data of the specified entity according to the specification of the entity from the user on the user screen and the update instruction of the specified entity.
The entity setting unit sets the data set of the entity by accepting the input of the item data to one or more items included in the form.
When the entity update unit accepts the input of the item data to the second item in the fourth entity designated by the user, the same item data as the item data of the key item in the fourth entity is used as the key item. A claim characterized in that when the set fifth entity exists, the item data of the second item in the fifth entity is set as the item data of the second item in the fourth entity. The server according to 1. The item data that can be input to the first item in the entity is set in advance with a tag.
The entity setting unit sets the data set of the entity by accepting the input of the item data to one or more items included in the form.
When the user screen providing unit accepts the input of the item data to the first item in the first entity designated by the user, and further, when the tag is specified by the user, the user screen providing unit inputs the item data corresponding to the tag. The server according to claim 1, wherein the server is displayed on the user screen as an input candidate for the first item in the first entity. Further equipped with a form setting unit for creating a form according to a form creation instruction from the user on the user screen.
The form setting unit sets the display attributes of the form according to the specifications from the user.
The user screen providing unit is characterized in that when displaying a list of a plurality of entities generated from the first form, the display method of the plurality of entities is changed according to the display attributes set in the first form. The server according to claim 1. Further equipped with a form setting unit for creating a form according to a form creation instruction from the user on the user screen.
The form setting unit defines the data structure of the form by activating the item specified by the user among a plurality of items prepared in advance in the form.
The entity setting unit sets the data set of the entity by accepting the input of the item data for the item enabled in the form.
Further, when the generation of the seventh entity based on the third form is instructed by using the sixth entity generated from the second form as the duplication source, in both the second form and the third form. The server according to claim 1, wherein the seventh entity is generated by including the item data of the sixth entity for the commonly activated items. An entity is a process management unit included in a product or service development project, and includes both schedule information including deadlines and progress information indicating the progress of the process as attribute values of the entity.
The server according to claim 1, wherein the user screen providing unit displays an achievement image which is a picture or a photograph showing the achievement of the process when the completion of the process is instructed in the progress information of the entity. Connected to multiple user terminals via a communication network,
A user screen providing unit that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to a user terminal.
An entity setting unit that creates an entity according to the user's selection of a form for the user screen and the instruction to create an entity based on the selected form.
It includes a deletion setting unit that sets a predetermined grace period for the selected form or entity according to the selection of the form or entity from the user on the user screen and the deletion instruction of the selected form or entity.
The deletion setting unit deletes the data of the form or the entity from the storage medium on condition that the grace period has elapsed , and sets the length of the grace period according to the attribute of the user instructed to delete. A server that features that. The deletion setting unit is characterized in that the setting of the grace period of the selected form or entity is canceled according to the selection of the form or entity from the user for the user screen and the resurrection instruction of the selected form or entity. The server according to claim 12 . Connected to multiple user terminals via a communication network,
A user screen providing unit that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to a user terminal.
An entity setting unit that creates an entity including process progress information according to the user's selection of a form for the user screen and the instruction to create an entity based on the selected form.
It is equipped with a deletion setting unit that deletes the data of the entity from the storage medium.
The deletion setting unit sets a grace period when the end setting is made in the progress information of the entity, deletes the data of the entity from the storage medium, and sets the end, on condition that the grace period has elapsed. A server characterized in that the grace period for the entity is canceled when the resurrection instruction for the entity is given during the grace period. A user screen display unit that displays a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form.
Of the multiple items prepared in advance in the form, the item input unit that accepts the specification of the item to be activated from the user,
Entity creation input part that accepts input of item data for the item enabled in the form ,
With a communication unit,
The user screen display unit hides the entity when the end is instructed in the progress information of the entity, and redisplays the hidden entity when the confirmation instruction is given by the user after the end instruction.
The communication unit is a user terminal characterized in that when a resurrection instruction is given to the redisplayed entity, the server is instructed to cancel the termination instruction of the entity. Includes one or more user terminals and servers interconnected via a communication network
The server
A user screen providing unit that provides a user screen that can display both a form that defines a data structure and an entity that is a data aggregate created according to the form to a user terminal.
An entity setting unit that creates an entity including process progress information according to the user's selection of a form for the user screen and the instruction to create an entity based on the selected form.
It is equipped with a deletion setting unit that deletes the data of the entity from the storage medium.
The user terminal is
The user screen display unit that displays the user screen and
Of the multiple items prepared in advance in the form, the item input unit that accepts the specification of the item to be activated from the user,
It is equipped with an entity creation input unit that accepts input of item data for items enabled in the form.
The entity setting unit of the server sets the data set of the entity by accepting the input of the item data to one or more enabled items contained in the form.
The deletion setting unit of the server sets a predetermined grace period when the termination setting is made for the entity, deletes the data of the entity from the storage medium , and deletes the data of the entity from the storage medium, provided that the grace period has elapsed. Set the length of the grace period according to the attribute of the user who set the end,
The user screen display unit of the user terminal is an information management system characterized in that the entity is hidden when the end setting is made for the entity or when the grace period has elapsed from the end instruction.

Images