WO2021250932A1 - Système de gestion d'informations, serveur, et terminal d'utilisateur - Google Patents

Système de gestion d'informations, serveur, et terminal d'utilisateur Download PDF

Info

Publication number
WO2021250932A1
WO2021250932A1 PCT/JP2021/004213 JP2021004213W WO2021250932A1 WO 2021250932 A1 WO2021250932 A1 WO 2021250932A1 JP 2021004213 W JP2021004213 W JP 2021004213W WO 2021250932 A1 WO2021250932 A1 WO 2021250932A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
user
item
data
screen
Prior art date
Application number
PCT/JP2021/004213
Other languages
English (en)
Japanese (ja)
Inventor
晃成 須藤
Original Assignee
株式会社ジュリア
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社ジュリア filed Critical 株式会社ジュリア
Publication of WO2021250932A1 publication Critical patent/WO2021250932A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to an information management technique.
  • Various software tools are provided for multiple users to share information. For example, by checking schedules using a group calendar and checking work progress using workflow software, an environment is being created in which a large number of users can easily collaborate even if they are geographically separated.
  • the project leader wants to have a wide view of the whole from R & D to fund management, but trying to know the details of the project in detail is rather unproductive due to the information overload.
  • Development engineers 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.
  • the present invention is an invention completed based on the above-mentioned problem recognition, and its main purpose 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 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 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.
  • a user screen provider 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.
  • 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.
  • 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.
  • an item input unit that accepts the designation of the item to be activated from the user
  • 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 for creating an entity including process progress information and a deletion setting unit for deleting entity data from a storage medium according to a form selection and an entity creation instruction 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 activated 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 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.
  • the "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.
  • the clothing manufacturer places an order for mass production from the "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.
  • Entities In the information management system described in this embodiment, information is managed in units called "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". Entity is 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).
  • 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.
  • a plurality of user terminals 110a, 110b ... 104n (hereinafter, collectively referred to as "user terminals 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. An entity ID and a form ID of the form from which the entity is derived are given to the entity.
  • the member setting unit 220 sets members 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 a user.
  • the friend setting unit 228 manages friend settings between users.
  • the method of setting friends is the same as that of general SNS (Social Networking Service).
  • SNS Social Networking Service
  • 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.
  • 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 an 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 the 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.
  • an entity is an information set
  • 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 items you want to use from the basic item group.
  • the entity Ea1 created from Form Fa also includes Item 1, Item 2, and Item 3, and the data corresponding to these three items (hereinafter referred to as “)”. It is called “item data").
  • the entity Eb1 created from the form Fb also includes the 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 items 1 and 4, that is, a part of the data structure is common.
  • 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 this 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.
  • Form F1 corresponds to "Mass production arrival schedule", Entity E11 “Mass production arrival schedule of bag a”, Entity E12 “Mass production arrival schedule of lesson bag b”, Entity E13 "Mass production arrival schedule 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".
  • one or more members are associated with the form.
  • 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.
  • the members of Form F2 are users P1 and P4.
  • the access authority to the entity E21 (manufacturing the design pattern of the hakama a) and the entity E22 (manufacturing the design pattern of the apron d) derived from the form F2 (manufacturing the design pattern) is limited to the users P1 and P4.
  • 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.
  • the user P4 can access only the entities E21 and E22.
  • User P5 cannot access any of the entities shown in FIG.
  • FIG. 5 is a screen view of the home screen 150.
  • 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.
  • 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.
  • a home button 152 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.
  • 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.
  • 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.
  • the form name "mass production scheduled to arrive" is input.
  • the form name is arbitrary.
  • Touching the cancel button 174 cancels the form creation.
  • 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 for mass production arrival), 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.
  • 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.
  • entity (F1) an 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.
  • entity setting unit 218 may publish the entity (F1) as a normal web page.
  • FIG. 8 is a screen view of the form second definition screen 190.
  • 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.
  • 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.
  • user P1 can add members to 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.
  • the friend setting unit 228 causes the user P1 to "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.
  • the user screen providing unit 214 uses the form F1 (mass production arrival schedule).
  • 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.
  • 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.
  • 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, a plurality of images can be registered 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.
  • the image registered in the image display area 310 is simply referred to as a "registered image”.
  • 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.
  • 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).
  • the registration button 314 of the image display area 310 is described as "clear".
  • the registration button 314 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.
  • User P1 inputs item data of other valid items while scrolling the entity creation screen 240.
  • the user P1 can input and confirm all the item data of the entity E11 (the mass production arrival schedule of the hakama a) by scrolling the entity creation screen 240.
  • 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.
  • the delete button 252 when creating a new entity E11 (scheduled for mass production of hakama), the entity E11 will not be saved. After creating the entity E11, the user can still edit the entity E11.
  • 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.
  • the cancel button 254 when creating a new entity E11 (scheduled for mass production of hakama), the entity E11 will not be saved.
  • the cancel button 254 while editing the entity E11, the entity E11 remains but the newly input item data is discarded without being registered.
  • the save button 258 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.
  • the form created by the user P1 (hereinafter referred to as "self-form") is displayed in a list in the creation form area 272.
  • 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 mass-produced) on the form list screen 270 (see FIG. 10).
  • the entity list screen 280 displays a list of entities derived from Form F1 (scheduled to be mass-produced) as thumbnails (extract images).
  • Thumbnail 282 is a thumbnail of the entity created on the entity creation screen 240 in FIG. 9 (scheduled mass production arrival of hakama a (entity name: new hakama set arrival)).
  • 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.
  • the user P1 can collectively confirm the schedule, progress status, and the like of the entity related to the form F1 (mass production arrival schedule).
  • 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.
  • the 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.
  • 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 set as “key items” in advance.
  • 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.
  • the entity creation screen 240 includes a plurality of image registration areas 244.
  • 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.
  • the user screen providing unit 214 highlights the processing button 320.
  • the user screen providing unit 214 highlights the processing button 320.
  • this user touches the completion button 322.
  • the user screen providing unit 214 highlights the completion button 322.
  • FIG. 13 is a screen view of the achievement screen 330.
  • 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.
  • 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).
  • an image praising that the user P2 has completed the entity E11 (scheduled for mass production of hakama a) is displayed, such as "NICE! MISSION COMPLETE".
  • 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.
  • 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.
  • 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).
  • the entity update unit 222 identifies the users P1, P2, and P3 that are members of the entity E11 (scheduled to be mass-produced in hakama), and the update notification unit 212 is a user P1 other than the user P2 who has completed the work.
  • An update notification is transmitted to P3 together with the user ID and entity ID of the user P2 (S12).
  • 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.
  • 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.
  • 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.
  • the entity E11 (scheduled for mass production of hakama a) is hidden, but the data is backed up on the server 200.
  • 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 a) 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. Entity E11 (scheduled for mass production of hakama a) is hidden in the user terminal 110 which is a member of 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 user screen providing unit 214 of the server 200 receives the grace confirmation request, the user screen providing unit 214 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.
  • the user P1 selects the entity to be revived from this list and then turns on the revival button (not shown).
  • 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.
  • the entity E11 is provided again to the users P1, P2, P3.
  • the deletion setting unit 302 resets the grace period when the deletion flag is turned off.
  • 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 deleted soon.
  • the entity can also be deleted when the user touches the delete button 252 on the entity creation screen 240.
  • entity E12 (scheduled for mass production of lesson bag b) is created and registered in the server 200. After that, it is assumed that the user P1 deletes the entity E12.
  • the deletion instruction is transmitted from the user terminal 110 to the server 200 together with the entity ID of the entity E12.
  • 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.
  • 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.
  • 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 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.
  • Entity created by a user other than user P1 and derived from another form in which 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.
  • 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 deleted 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 schedule of the entity related to him / her on the calendar screen 340.
  • the user can narrow down the entities to be displayed on the calendar from the entities of which the user 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, an entity including "X" as the item data as the key item "product number” is described 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, and E32 are derived do not have to be the same.
  • the image R1 is selected as the registered image.
  • the images R2 and R4 are selected as registered images.
  • 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.
  • 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).
  • 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 an 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.
  • 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 one of the images from the related image selection screen.
  • the selection result is transmitted from the user terminal 110 to the server 200.
  • the related image button 306 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, there are three types of related images that can be used when the user P1 creates the entity E41 (KEY: 12047): 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 on 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.
  • the preparation image selection screen (not shown) is displayed. The user can set the registered image of the entity E41 by selecting one of the prepared images from the prepared image selection screen. The relationship between the tag and the prepared image will be described later.
  • 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.
  • the user P1 may set an image of a product as a registered image.
  • the registered image can be selected from the images stored in 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.
  • the prepared image is identified by the image ID.
  • 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.
  • the preparation image selection screen in which the preparation images U1 and U2 can be selected is displayed.
  • 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.
  • 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.
  • the user P1 selects "date” as the display order of the form F1.
  • 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.
  • the user screen providing unit 214 displays the entities (F1) in the order of the product number.
  • the user P1 can confirm the entities (F1) in order from the oldest start date and time, and the entities (F1) having the same product number can be confirmed. You can also check the contents of.
  • FIG. 20 is a schematic diagram for explaining a method of replicating an entity.
  • the entity EX generated from the form FX is duplicated to generate the entity EY.
  • the entity EY is based on a form FY different from the form FX.
  • the user P1 touches the duplicate button 256 on the entity creation screen 240 of the entity EX (FX) (see FIGS. 9 and 12).
  • 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.
  • 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). ..
  • item 2 of entity EX is not enabled in 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.
  • the information management system 100 has been described above based on the embodiment.
  • 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 items determine the quality and quantity of entity information.
  • the form (mass production arrival schedule (overall)) includes the minimum valid items such as product number and schedule
  • the form (mass production arrival schedule (site)) includes the price, return rate, and display shelves to be secured at the time of arrival. Items such as the location of may be enabled in detail.
  • the manager may confirm the entity derived from the form (mass production arrival schedule (overall)), and the field 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.
  • the server 200 turns on the deletion flag of the entity, sets a grace period, and automatically deletes the data of the entity.
  • the amount of work to delete the entity is also huge.
  • Automatic deletion of entities is also effective in preventing information leaks that were necessary in the past but are no longer necessary.
  • 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.
  • a registered image of an 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", it becomes easy to intuitively understand which product number the entity is related to when browsing the entity on the entity list screen 280 or the like.
  • 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.
  • 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".
  • the entity E11 is created, the user P1 does not need to perform another operation for associating the product number “12074” with the image R1.
  • the tag and the prepared image are associated in advance.
  • 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.
  • 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.
  • the display order of the entities can be freely changed.
  • “date” and “product number” are exemplified, but the display order may be changed based on other items.
  • the display order of the thumbnail 282 (FIG. 11) on the entity list screen 280 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.
  • an entity EY based on another form FY can be duplicated from the entity EX based on the form FX.
  • an entity EX related to design confirmation of children's shoes c it may be desired to newly create an entity EY related to procurement of prototype materials for children's shoes c.
  • a new entity EY (prototype material procurement for children's shoes c) may be newly generated based on the form FY (prototype material procurement), but entity EX (design confirmation of children's shoes c) and entity EY (children's shoes c). It is thought that many of the item data of (Prototype material procurement) are likely to be the same.
  • 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.
  • the user may freely change the item data initially set 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, an entity (design confirmation of the boots d).
  • the related image sharing function described in relation to FIGS. 16 and 17 and the entity duplication function described in relation to FIG. 20 it becomes easier to unify the registered images for each product or project. ..
  • the image R6 is used as a registration image of the entity EX for the "children's shoes c"
  • 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.
  • the image R6 is duplicated as a registered image even in the newly generated entity of "children's shoes c"
  • 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.
  • 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.
  • 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.
  • 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.
  • some components may be deleted from all the components shown in the above embodiments and modifications.
  • the schedule management of the project related to the design of children's clothing has been described.
  • 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.
  • 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.
  • 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 entities in the grace folder. When the user of the user terminal 110 selects a resurrection target entity 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.
  • the entity is deleted, but the form may be deleted.
  • the form 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).
  • 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.
  • the form 1 definition screen 180 is displayed for the form F1
  • the calendar button 304 is set to set whether or not to display all the entities derived from the form F1 on the calendar screen 340.
  • 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.
  • the registered image of the existing entity is selected as the related image.
  • item data other than the image may be presented as a selection candidate.
  • texts such as explanatory texts, music, videos, and the like may be presented as selection candidates as related data.
  • 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).
  • 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).
  • the entity setting unit 218 may automatically set the data DC in the item 1 of the entity EA (KEY: X).
  • the user screen providing unit 214 presents the registered images of the entities E2 and E3 as related images when the entities E2 and E3 whose key data of each of the key items Q1 and Q2 exactly 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.
  • 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. , Positions, etc., as long as the information can be categorized by 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 5 times or less, 6 to 10 times, and 10 times or more of completion of the entity 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.
  • an achievement count detection unit (not shown) that counts the achievement count for each user.
  • 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.
  • the entity setting unit 218 of the server 200 may propose to the entity creator to delete an entity with little 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.
  • Form setting unit 216 may propose to delete a form that does not have an entity.
  • the entity setting unit 218 may propose to delete an entity related to an old schedule, for example, an entity related to a schedule one year or more ago.
  • 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 a user terminal 110, and a user's schedule and memorandum may be managed for each entity only by the user terminal 110.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Educational Administration (AREA)
  • Development Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Hardware Design (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

Selon un mode de réalisation de la présente invention, un serveur est relié à une pluralité de terminaux d'utilisateurs par l'intermédiaire d'un réseau de communication. Le serveur fournit aux terminaux d'utilisateurs un écran d'utilisateur capable d'afficher aussi bien un formulaire (catégorie) qui définit une structure de données qu'une entité (planning) qui est un agrégat de données créé selon le formulaire. Le serveur crée une entité comprenant des informations d'avancement de planning selon une commande de création d'entité basée sur une sélection de formulaire effectuée par un utilisateur sur l'écran d'utilisateur, et le formulaire sélectionné. Lorsqu'un réglage d'arrêt est effectué par rapport aux informations d'avancement d'une entité, une partie de réglage de suppression spécifie une période de grâce prédéterminée, et supprime d'un support de stockage des données de l'entité à la condition que la période de grâce se soit écoulée.
PCT/JP2021/004213 2020-06-12 2021-02-05 Système de gestion d'informations, serveur, et terminal d'utilisateur WO2021250932A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-102448 2020-06-12
JP2020102448A JP7026410B2 (ja) 2020-06-12 2020-06-12 情報管理システム、サーバおよびユーザ端末

Publications (1)

Publication Number Publication Date
WO2021250932A1 true WO2021250932A1 (fr) 2021-12-16

Family

ID=78847143

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/004213 WO2021250932A1 (fr) 2020-06-12 2021-02-05 Système de gestion d'informations, serveur, et terminal d'utilisateur

Country Status (2)

Country Link
JP (1) JP7026410B2 (fr)
WO (1) WO2021250932A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015011650A (ja) * 2013-07-02 2015-01-19 富士通株式会社 プロジェクトのリスケジュール方法及びプログラム
JP2018132927A (ja) * 2017-02-15 2018-08-23 カシオ計算機株式会社 作業支援装置及びプログラム
JP2019133475A (ja) * 2018-01-31 2019-08-08 日本ビジネスシステムズ株式会社 タスク管理サーバシステム、タスク管理システム及びプログラム

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5018689B2 (ja) * 2008-08-12 2012-09-05 株式会社Ｊｖｃケンウッド 車載器、コンテンツ情報処理方法及びプログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015011650A (ja) * 2013-07-02 2015-01-19 富士通株式会社 プロジェクトのリスケジュール方法及びプログラム
JP2018132927A (ja) * 2017-02-15 2018-08-23 カシオ計算機株式会社 作業支援装置及びプログラム
JP2019133475A (ja) * 2018-01-31 2019-08-08 日本ビジネスシステムズ株式会社 タスク管理サーバシステム、タスク管理システム及びプログラム

Also Published As

Publication number Publication date
JP7026410B2 (ja) 2022-02-28
JP2021196825A (ja) 2021-12-27

Similar Documents

Publication Publication Date Title
US11057388B2 (en) Method and computer program product for creating enterprise management systems
JP5983808B2 (ja) 情報処理方法、表示方法、情報処理装置、端末装置、情報処理プログラム及び表示プログラム
JP7026410B2 (ja) 情報管理システム、サーバおよびユーザ端末
JP6942375B2 (ja) 情報管理システム、サーバおよびユーザ端末
JP6942374B2 (ja) 情報管理システム、サーバおよびユーザ端末
JP6060334B1 (ja) 訪問者検索システムおよび訪問者検索プログラム
JP6845365B1 (ja) 対話型入力支援システム、対話型入力支援方法、情報処理システム及びプログラム
JP2015158754A (ja) 訪問サービス支援システム
JP2003150644A (ja) 関係付け情報管理システム、関係付け情報管理用プログラム、及び記録媒体
EP1160715A2 (fr) Système informatique pour la conservation de données et le contrôle de processus
JP2004287584A (ja) 作業スケジュール表の表示方法、作業管理方法およびシステム
JP7437046B2 (ja) 年史制作方法、プログラム、年史制作装置および年史制作システム
JP3358734B2 (ja) 教育・保育機関における情報の処理方法、処理装置及び処理プログラム
JP3535807B2 (ja) アイデア管理システム、アイデア管理方法、アイデア提案装置及び記録媒体
EP1158444A1 (fr) Logiciel d'application personnalisable commandé par données
JP4134594B2 (ja) テーマ管理システム及びそのプログラム
JP2007272425A (ja) 作業状況管理支援システム、作業状況管理支援方法、及びプログラム
JP2024077746A (ja) プログラム、方法、およびシステム
Lewis et al. Incorporating Diversity, Equity, and Inclusion Principles into Our Metadata
JP3657228B2 (ja) 教育・保育機関における情報の処理方法、処理装置及び処理プログラム
JP2002163429A (ja) ワークフロー管理システム、サーバ、及び、記録媒体
JP2003150843A (ja) 広告情報配信方法及び広告情報配信システム
Farkaš SharePoint platform implementation
JP2002024505A (ja) 情報管理システム、情報管理方法、サーバ、及び、記録媒体
Sulaiman Real Time Updating System for Dynamic Report UTP Energy Website Enhancement: Delivering Real Time Mission Oriented Research Information Reports

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21821011

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21821011

Country of ref document: EP

Kind code of ref document: A1