Clothing management system and program

Abstract

The present invention provides a clothing management system 10 that can determine the optimal timing for suggesting the disposal of clothing and shoes to the user. [Solution] The clothing management system 10 includes a user terminal 20 owned by the user and a management server 30. The user registers the purchase price of the clothing and usage information regarding the wearing of the clothing with the management server using the user terminal. The management server 30 calculates the cost per wear by dividing the purchase price of the clothing by the number of times the clothing has been worn, and decides to suggest (notify) the disposal of the clothing based on the fact that the cost per wear falls below a threshold cost. The user terminal 20 receives the notification from the management server and displays a disposal suggestion screen on the touch panel 24 that suggests the disposal of the clothing. The user registers that the clothing has been disposed of with the management server 30 via the user terminal 20.

Description

【Technical Field】 【0001】 The present invention relates to a system that provides a user with a management service for clothing and the like stored in storage spaces such as closets and shoe boxes through a user terminal possessed by the user, and a program used in the system. 【Background Art】 【0002】 Clothing is stored and kept in closets, chests of drawers, etc. If the number of clothes purchased is greater than the number of clothes discarded, the amount of clothing increases and compresses the storage space. The same is true for shoes. 【0003】 Patent Document 1 discloses a clothing management system in a house. This management system stores by associating a management number of clothing and the purchase date. The management system proposes (notifies) to the user to discard clothing for which a certain period has elapsed since the purchase date. 【Prior Art Documents】 【Patent Documents】 【0004】 【Patent Document 1】 Japanese Unexamined Patent Application Publication No. 2014-142857 【Summary of the Invention】 【Problems to be Solved by the Invention】 【0005】 Generally, clothing is purchased according to its intended use. Types of clothing include, for example, fashionable clothing for going out, everyday clothing for daily wear, and loungewear for wearing at home. Fashionable clothing tends to be relatively expensive and used infrequently. Everyday clothing and loungewear tend to be relatively inexpensive and used frequently. The management system disclosed in Patent Document 1 uniformly determines whether or not to discard clothing based on the time elapsed since the purchase date, so the type of clothing, frequency of use, and purchase price are not taken into consideration when deciding whether to discard. As a result, the above management system suggests discarding both expensive fashionable clothing that is used infrequently and inexpensive loungewear that is used frequently after a certain period of time. However, users often do not want to discard expensive fashionable clothing that is used infrequently, even after a certain period of time has passed. Consequently, even if the above management system suggests discarding, the user must decide whether or not to discard it, and if the user is unable to make a decision, there is a risk that the disposal of clothing will be postponed. 【0006】 This invention has been made in view of the circumstances described above, and its purpose is to provide a means for notifying users of the timing for discarding clothing and other items, taking into account the purchase price and number of times they have been used. [Means for solving the problem] 【0007】 (1) The clothing management system according to the present invention comprises a user terminal having an input interface, a first communication interface, a display, and a first controller, and a management server having a second communication interface, server memory, and a second controller. The first controller performs a management information acquisition process to acquire management information including the purchase price of a managed item, which is clothing or shoes, and usage information of the managed item, and a management information transmission process to transmit the management information to the management server via the first communication interface and the Internet. The second controller performs a management information registration process to store the received management information in the server memory in association with managed item identification information, a first determination process to determine whether the usage unit price calculated by dividing the purchase price by the number of uses indicated by the usage information is less than a threshold unit price, and a first disposal notification transmission process to transmit disposal notification information for a specific managed item, which is the managed item for which the first determination process determined that the usage unit price is less than the threshold unit price, to the user terminal via the second communication interface and the Internet. Based on receiving the above-mentioned disposal notification information, the first controller executes a display process to display a disposal suggestion screen on the display indicating the disposal of the specified managed object. 【0008】 The cost per use is calculated by dividing the purchase price by the number of uses, so it is a value that decreases each time clothing is used. In other words, the cost per use is an indicator of whether clothing has been used a number of times commensurate with the purchase price. For clothing that is determined in the first judgment process to have a cost per use below the threshold cost, the user is notified of disposal. In other words, the timing of disposal of clothing is notified to the user, taking into account the purchase price and the number of times the clothing has been used. The user disposes of the clothing that has been notified of disposal, after being convinced that it has been used a sufficient number of times commensurate with the purchase price. 【0009】 (2) The managed items may be clothing. The management information includes the user's weight at the time of purchase of the managed items. The first controller performs a latest weight transmission process to send the latest weight entered through the input interface to the management server through the first communication interface. The second controller performs a second determination process to determine whether the weight difference calculated by subtracting the purchase weight from the latest weight is greater than or equal to a threshold weight, and a second disposal notification transmission process to send disposal notification information for the specific managed items for which the second determination process determined that the weight difference is greater than or equal to the threshold weight to the user terminal via the second communication interface and the Internet. 【0010】 The weight difference, calculated by subtracting the weight at the time of purchase from the current weight, is an indicator of changes in body shape between the time of purchase and the present. If the weight difference exceeds a threshold weight and the second judgment process determines that the clothing is difficult to wear, the user will also be notified of the need to discard the clothing. 【0011】 (3) The management information may include maintenance information relating to maintenance performed on the managed object. The second controller performs a first calculation process to calculate a maintenance point index that quantifies the frequency of maintenance performed on the managed object based on the maintenance information, and a third determination process to determine whether the maintenance point index is less than a threshold index. The first disposal notification transmission process is a process that transmits disposal notification information for a specific managed object, which is a managed object for which the first determination process has determined that the usage unit price is less than the threshold unit price, and the third determination process has determined that the maintenance point index is less than the threshold index, to the user terminal via the second communication interface. 【0012】 Even if the unit price per use is below the threshold unit price and the clothing has been used a sufficient number of times relative to the purchase price, if the clothing has been properly maintained, the user is unlikely to agree to its disposal, and it is appropriate to exclude it from the disposal notification. Whether or not clothing has been properly maintained is determined by whether or not the maintenance point index, which indicates the frequency of maintenance, is below the threshold index. Therefore, the timing of notifying users of disposal can be determined more appropriately than when it is determined solely by the unit price per use. 【0013】 (4) The second controller may perform a second calculation process for each managed object, which calculates a favorite score indicating the user's level of liking based on the frequency of use indicated by the number of uses and the period of use, and a fourth determination process, which ranks the managed objects based on the favorite score and determines whether the rank is below a threshold rank. The first disposal notification transmission process is a process that transmits disposal notification information to the user terminal via the second communication interface for a specific managed object, which is determined in the first determination process to have a usage cost below a threshold cost and whose rank is determined to be below a threshold rank in the fourth determination process. 【0014】 Even if the unit price per use is below a threshold unit price and the clothing has been used a sufficient number of times relative to the purchase price, it is appropriate to exclude clothing that the user likes from the list of items to be discarded. Whether or not a piece of clothing is liked by the user is indicated by a ranking determined by the frequency of use. Clothing with a high ranking will be excluded from the list of items to be discarded. Therefore, the timing of notifying users of discarding items can be determined more appropriately than when the unit price per use is used alone. 【0015】 (5) The management information may include maintenance information relating to maintenance performed on the managed object. The second controller performs a first calculation process to calculate a maintenance point index that quantifies the frequency of maintenance performed on the managed object based on the maintenance information. The second calculation process includes a process to correct the favorite score by the maintenance point index, or by the maintenance point index and the specified favorite score entered by the user. 【0016】 By adjusting the favorite score based on the maintenance points index, or the maintenance points index and the user's specified favorite score, the timing for notifying the user of disposal can be determined more appropriately. 【0017】 (6) The management information above includes category information indicating the type of managed object, and the category information may be associated with a weight coefficient. The second controller performs a correction process to correct the usage unit price or the threshold unit price by the weight coefficient. 【0018】 Since the unit price or threshold unit price is adjusted by a weighting coefficient indicated by the type of clothing, etc., the timing of notifying the user of disposal can be determined more appropriately. 【0019】 (7) The management information described above includes category information indicating the type of managed object, and the category information may be associated with a first decision date before the estimated use period of the managed object and a second decision date after the estimated use period. The first decision process described above is performed on the first decision date and the second decision date for the managed object of the type associated with the first decision date and the second decision date. 【0020】 The types of items managed include spring, summer, autumn, and winter clothing. For summer items such as summer clothes and sandals, a decision on whether or not to discard them is made on the first and second decision dates, before and after the summer season (estimated usage period), such as April and October, and the user is notified accordingly. Therefore, the timing of notifying users of the need to discard items can be determined more appropriately. 【0021】 (8) The clothing management system according to the present invention comprises a user terminal having an input interface, a first communication interface, a display, and a first controller, and a management server having a second communication interface, server memory, and a second controller. The first controller performs a management information acquisition process to acquire management information including the user's weight at the time of purchase, which is the user's weight at the time of purchase of the managed item, which is clothing; a management information transmission process to transmit the management information to the management server via the first communication interface and the Internet; and a latest weight transmission process to transmit the latest weight entered via the input interface to the management server via the first communication interface. The second controller performs a management information registration process to store the received management information in the server memory in association with managed item identification information and to store the latest weight in the server memory; a determination process to determine whether the weight difference calculated by subtracting the weight at purchase from the latest weight is greater than or equal to a threshold weight; and a disposal notification transmission process to send disposal notification information to the user terminal for the specific managed item, which is the managed item, for which the determination process determined that the weight difference is greater than or equal to the threshold weight. Based on receiving the above-mentioned disposal notification information, the first controller executes a display process to display a disposal suggestion screen on the display indicating the disposal of the specified managed object. 【0022】 (9) The program according to the present invention is implemented on a user terminal including an input interface, a communication interface, a display, and a computer. The program causes the computer to execute a management information reception process of receiving, through the input interface, input of management information including type information indicating the type of a management object, which is purchased clothing or shoes, and the purchase amount; a management information transmission process of transmitting the management information to a management server through the communication interface and the Internet; a usage information reception process of receiving, through the input interface, input of usage information indicating the number of times of use of the management object; a usage information transmission process of transmitting the usage information to the management server through the communication interface; and a display process of receiving discard notification information transmitted by the management server and causing the display to display a specific management object, which is the management object indicated by the discard notification information. 【0023】 The present invention can also be regarded as a program implemented on a user terminal. 【0024】 (10) The program according to the present invention is a program implemented on a user terminal including an input interface, a communication interface, a display, and a computer. The program causes the computer to execute a management information reception process of receiving, through the input interface, input of management information including type information indicating the type of purchased clothing and the weight at the time of purchase; a management information transmission process of transmitting the management information to a management server through the communication interface and the Internet; a latest weight reception process of receiving, through the input interface, input of the latest weight; a latest weight transmission process of transmitting the latest weight to the management server through the communication interface; and a display process of receiving discard notification information transmitted by the management server and causing the display to display a specific piece of clothing, which is the clothing indicated by the discard notification information. 【0025】 The present invention can also be regarded as a program implemented on a user terminal. 【Effects of the Invention】 【0026】 The clothing management system according to the present invention can notify the user of the timing of discarding clothing and the like in consideration of the purchase amount and the number of uses of the clothing and the like. 【Brief Description of the Drawings】 【0027】 [Figure 1] FIG. 1 is a configuration diagram and a functional block diagram of a clothing management system 10 according to an embodiment. [Figure 2] FIG. 2(A) is a diagram showing a user management database, and FIG. 2(B) is a diagram showing a clothing management database. [Figure 3] FIG. 3(A) is a diagram showing a cleaning score conversion table, FIG. 3(B) is a diagram showing a weighting table, FIG. 3(C) is a diagram showing a judgment date correspondence table, FIG. 3(D) is a diagram showing a cleaning score conversion table according to a modified example, and FIG. 3(E) is a diagram showing a weighting table according to a modified example. [Figure 4] FIG. 4 is a flowchart showing the registration of management information. [Figure 5] FIG. 5 is a flowchart showing the registration of maintenance information and the like. [Figure 6] FIG. 6 is a part of a flowchart for judging and notifying the discard of clothing. [Figure 7] FIG. 7 is another part of a flowchart for judging and notifying the discard of clothing. [Figure 8] FIG. 8(A) is a diagram showing a user registration screen, and FIG. 8(B) is a diagram showing a part of a clothing registration screen. [Figure 9] FIG. 9(A) is a diagram showing another part of a clothing registration screen, and FIG. 9(B) is a diagram showing a first clothing selection screen. [Figure 10] FIG. 10(A) is a diagram showing a second clothing selection screen, and FIG. 10(B) is a diagram showing a clothing details screen. [Figure 11] FIG. 11(A) is a diagram showing a part of a third maintenance information registration screen, and FIG. 11(B) is a diagram showing another part of the third maintenance information registration screen. [Figure 12] Figure 12(A) shows the first notification screen, and Figure 12(B) shows the decision execution screen. [Figure 13] Figure 13(A) shows the waste suggestion screen, and Figure 13(B) shows the clothing confirmation screen. [Figure 14] Figure 14(A) shows a user management database related to a modified version, and Figure 14(B) shows a shoe management database related to a modified version. [Modes for carrying out the invention] 【0028】 Embodiments of the present invention will be described below. It goes without saying that the embodiments described below are merely examples of the present invention, and the embodiments of the present invention can be modified as appropriate without changing the gist of the invention. Furthermore, the execution order of each process (each step) shown in the flowcharts from Figures 4 to 7 may be changed as appropriate without changing the gist of the present invention, some may be omitted, other processes may be added, or they may be replaced with other equivalent processes. 【0029】 [Overview of Clothing Management System 10] The clothing management system 10 (see Figure 1) described in this embodiment is a system that provides a clothing management service to a user. For example, the service is provided to one family member residing in a house. Alternatively, the service is provided to multiple family members residing in a house. The user receives the service by downloading an application program provided by the service provider (hereinafter also referred to as the "service provider") to a terminal owned by the user. 【0030】 The service provider is, for example, a company that built a house. The service provider offers services using the clothing management system 10 as one of the various services they provide to the homeowner and their family. These various services include, for example, services related to home maintenance and services that support comfortable living in the home. The clothing management system 10 is operated in conjunction with other service systems. For example, the clothing management system 10 provides data used by other systems. Alternatively, the clothing management system 10 acquires data necessary for operation from other systems. In other words, the clothing management system 10 also functions as a data collection system for other systems. 【0031】 However, the clothing management system 10 may be operated as a standalone system, or it may be operated by a business other than the business that constructed the house. 【0032】 In this embodiment, an example is described in which the clothing management system 10 is used for managing clothing (items to be managed). 【0033】 [Configuration of the clothing management system 10] As shown in Figure 1, the clothing management system 10 comprises a user terminal 20 owned by the user and a management server 30. 【0034】 [User terminal 20] User terminal 20 is a communication terminal owned by the user and capable of connecting to the internet. User terminal 20 may be, for example, a smartphone (registered trademark), a tablet (registered trademark), or a personal computer. 【0035】 The user terminal 20 comprises a central processing unit (CPU) 21, terminal memory 22, a communication interface 23, a touch panel 24, and a camera 25, as well as a communication bus (not shown) connecting them. The CPU 21 is an example of a first controller and computer. 【0036】 The terminal memory 22 is composed of, for example, ROM, RAM, and EEPROM, and other memory elements. The terminal memory 22 may be composed of any type of memory element. 【0037】 The terminal memory 22 stores the operating system OS 26 and the downloaded application program 27 (hereinafter also referred to as "app 27"). App 27 is a program that, together with the management program 35 described later, executes the processes (flows) shown in Figures 4 to 7. App 27 is an example of a program. 【0038】 The communication interface 23 is an interface that connects to the Internet 11 via an access point using short-range wireless communication such as Wi-Fi, or an interface that connects to the Internet 11 via a mobile communication network. The communication interface 23 is an example of a first communication interface and a communication interface. 【0039】 The touch panel 24 has a display and a transparent, film-like touch sensor superimposed on the display. The touch panel 24 is an example of a display and input interface. The user terminal 20 may also have a microphone that accepts voice input as an input interface. Alternatively, the user terminal 20 may have a display and input interface instead of the touch panel 24. The input interface may be, for example, a keyboard, a mouse, and a microphone. 【0040】 Camera 25 is a so-called digital camera equipped with multiple image sensors. Camera 25 generates image data through imaging. Camera 25 is used to image clothing. 【0041】 [Management Server 30] The management server 30 is a server that publishes a communication address on the internet 11. The management server 30 may be a server owned by the service provider, or it may be a rental server for which the service provider has usage rights. The management server 30 may be a single server, or it may be a cloud server composed of multiple servers, including a storage server. 【0042】 The management server 30 comprises a central processing unit (CPU) 31, server memory 32, and a communication interface 33, as well as a communication bus (not shown) connecting them. The CPU 31 is an example of a second controller. 【0043】 The communication interface 33 is connected to, for example, a gateway device (not shown) connected to the Internet 11. In other words, the management server 30 is connected to the Internet 11 via the gateway device. The communication interface 33 is an example of a second communication interface. 【0044】 The server memory 32 is composed of, for example, ROM, RAM, EEPROM, hard disk drives, solid-state drives, USB memory, and other memory elements and storage devices. Furthermore, a portion of the server memory 32 may be composed of a storage server. 【0045】 Server memory 32 stores the operating system OS 34, the management program 35, the management database, and the correspondence tables. 【0046】 The management program 35 is a program that, together with the application 27, executes the processes (flows) shown in Figures 4 to 7. 【0047】 The management database includes the user management database shown in Figure 2(A) and the clothing management database shown in Figure 2(B). The management database has data that represents tables and a control program that performs operations such as registering data to and reading data from tables. The management program 35 instructs the control program to read or register (write) data via the OS 34. The control program may be part of the management program 35. 【0048】 [User Management Database] The user management database shown in Figure 2(A) is a database that manages data (information) about users. 【0049】 The user management database has multiple columns and records, each labeled with the following names: "User ID," "Name," "Gender," "Age," "Quantity," "Current Weight," and "Target Unit Price." 【0050】 Each field in the column named "User ID" is registered with a User ID, which is identification information that identifies each user. Each record (each user) is identified by its User ID. When the application 27 is downloaded by a user, the management program 35 generates a new User ID and sends it to the user terminal 20, and also generates a new record in the user management database and registers the newly generated User ID in the newly generated record. 【0051】 Each field in the column named "Name" will contain the user's name. Each field in the column named "Gender" will contain the user's gender, either "Male," "Female," or "Other." Each field in the column named "Age" will contain the user's age. The user's name, gender, and age are sent from the user terminal 20 to the management server 30 when the application 27 is downloaded by the user, and are registered in the user management database by the management program 35. 【0052】 Each column named "Quantity" has multiple sub-columns named "Spring Items," "Summer Items," "Autumn Items," "Winter Items," "Year-Round Items," and "Total." 【0053】 Each field in the subcolumn named "Spring Clothes" registers the number of spring clothes owned by the user. Each field in the subcolumn named "Summer Clothes" registers the number of summer clothes owned by the user. Each field in the subcolumn named "Autumn Clothes" registers the number of autumn clothes owned by the user. Each field in the subcolumn named "Winter Clothes" registers the number of winter clothes owned by the user. Each field in the subcolumn named "Year-Round Clothes" registers the number of year-round clothes owned by the user. Each field in the subcolumn named "Total" registers the total number of clothes owned by the user. The management program 35 calculates the number of spring, summer, autumn, winter, and year-round clothes, as well as the total number of clothes, based on the data registered in the clothing management database, and registers them in the user management database. The number of each type of clothing and the total number are sent to the user terminal 20, for example, upon request from the user. 【0054】 Each field in the column named "Latest Weight" registers the user's current (latest) weight. The user enters their latest weight into the user terminal 20, sends it from the user terminal 20 to the management server 30, and the management program 35 registers it in the user management database. For example, application 27 periodically displays a screen on the touch panel 24 requesting and accepting input of the user's latest weight. 【0055】 Each field in the column named "Target Cost Per Item" registers the target cost per item. The target cost per item is a threshold used to determine whether or not to discard clothing. When the app 27 is downloaded by the user, the target cost per item is sent from the user terminal 20 to the management server 30 and registered in the user management database by the management program 35. Alternatively, after the app 27 is downloaded, the app 27 displays a screen on the touch panel 24 requesting and accepting input of the target cost per item. The target cost per item is an example of a threshold cost. 【0056】 [Clothing Management Database] The clothing management database shown in Figure 2(B) is a database that individually identifies the clothing owned by a user and manages data (information) related to that clothing. The data registered in the clothing management database is an example of management information. Note that the management information may include information other than that shown in Figure 2(B). 【0057】 The clothing management database has multiple columns, each labeled with the following names: "User ID," "Clothing ID," "Purchase Date," "Price," "Category 1," "Category 2," "Handling Instructions," "Weight at Purchase," "Hanger Number," "Specified Favorite Rating," "Elapsed Time (m)," "Number of Wears (B)," "Price per Wear," "Care Points," "Favorite Rating Score," "Favorite Rating Rank," "Photo Data," "Decision Date," "Decision Confirmed Flag," and "Disposal Confirmation Flag." 【0058】 Each field in the column named "User ID" will contain the User ID. 【0059】 Each field in the column named "Clothing ID" registers a clothing ID, which is identification information that identifies each piece of clothing individually. When a user registers clothing in the clothing management system 10 using the application 27, the management program 35 generates a new clothing ID and a new record, and registers the generated new clothing ID and the user ID of the user making the registration in the new record. The clothing ID is an example of managed identification information. 【0060】 Each record is individually identified by a user ID and a garment ID. Each record contains data (information) related to one garment. 【0061】 Each field in the column named "Purchase Date" will contain the date the user purchased the clothing. 【0062】 Each field in the column named "Amount" will contain the purchase price (price) of the clothing items purchased by the user. 【0063】 Each field in the column named "Category 1" will register one of the following types of clothing purchased by the user: "Stylish Clothes," "Everyday Clothes," or "Loungewear." Note that Category 1 may also contain other types of clothing besides "Stylish Clothes," "Everyday Clothes," and "Loungewear." 【0064】 Each field in the column labeled "Classification 2" will contain one of the following categories of clothing purchased by the user: "Spring," "Summer," "Autumn," "Winter," or "All-season." 【0065】 In the column named "Handling Instructions," each field will register the handling instructions displayed on the garment's tag, such as "Do not wet clean," "Do not iron at high temperatures," and "Dry in the shade." 【0066】 Each field in the column named "Weight at Purchase" will contain the user's weight at the time of purchase. 【0067】 Each field in the column named "Hanger Number" will register the hanger number assigned to the hanger on which the user is hanging their clothes. Note that if a hanger does not have a hanger number, it does not need to be registered. The hanger number, which has a one-to-one correspondence with the clothing ID, is an example of managed identification information. 【0068】 The purchase date, purchase price, category 1, category 2, care instructions, weight at purchase, and hanger number of each garment are entered by the user into the user terminal 20 using the app 27, either individually at the time of purchase or collectively when the app 27 is downloaded. The management program 35 registers the purchase date and other information transmitted by the user terminal 20 into the garment management database. 【0069】 The column named "Specified Favorite Rating" has two sub-columns named "Initial Purchase" and "Latest Purchase". The field in the sub-column named "Initial Purchase" registers the user's subjective favorite rating of the clothing at the time of purchase. The field in the sub-column named "Latest Purchase" registers the user's subjective favorite rating of the clothing now, after the purchase. 【0070】 The designated favorite rating is registered as a 5-point scale, for example, from "1" to "5". The designated favorite rating (initial) is entered by the user using app 27 into the user terminal 20, either individually when purchasing clothing or collectively when downloading app 27. The designated favorite rating (latest) is entered by the user using app 27 into the user terminal 20 after a certain period of time has passed, such as one year after purchasing clothing, or before making a decision on whether or not to discard clothing. The management program 35 registers the designated favorite ratings sent by the user terminal 20 into the clothing management database. 【0071】 Each field in the column named "Elapsed Period m" registers the elapsed period from the date of purchase of the clothing to the present. The elapsed period m can be in days or years. For example, for clothing purchased less than one year ago, "1" is registered to indicate the first year, and for clothing purchased more than one year but less than two years ago, "2" is registered to indicate the second year. "m" is an integer greater than or equal to "1" that indicates how many years have passed since the purchase date. In this embodiment, the elapsed period m is in years. The management program 35 calculates the elapsed period m based on the purchase date and the current date and updates it periodically. The elapsed period m is an example of a period of use. 【0072】 Each field in the column named "Number of Wears B" registers the number of times the user has worn the garment from the date of purchase to the present. Based on having worn the garment, the user enters usage information indicating that the garment has been worn into the user terminal 20 using the application 27. The management program 35 increments the "Number of Wears B" (by "1") based on receiving the usage information sent by the user terminal 20. The "Number of Wears" is an example of usage information and usage count. 【0073】 Each field in the column named "Cost per Wear" registers the purchase price of the garment and the cost per wear calculated from the number of times the garment has been worn (B). The management program 35 calculates the cost per wear by dividing the purchase price of the garment by the number of times the garment has been worn, for example, based on an update to the number of times the garment has been worn, or just before deciding to discard the garment, and registers it in the garment management database. In the case of a fashionable garment identified by garment ID "002", the purchase price is "14,900 yen" and the number of times it has been worn is "12 times", so the cost per wear is 14,900 / 12 = 1240 (rounded down to the nearest 10). The cost per wear is used to decide whether or not to suggest (notify) the disposal of the garment. The cost per wear is an example of a cost per wear. 【0074】 Each field in the column labeled "Maintenance Points" registers maintenance points, which are numerical values ​​representing the total maintenance performed by the user on their clothing. Maintenance includes washing, ironing, and dry cleaning. When a user performs maintenance on their clothing, they input maintenance information, including the type of maintenance (such as washing) and the clothing that was maintained, into the user terminal 20 using the application 27. The management program 35 uses the received maintenance information and the "Maintenance Point System Table" shown in Figure 3(A) to assign points to the maintenance performed by the user on their clothing and register (add) them to the clothing management database. The maintenance points registered in the fields of the column labeled "Maintenance Points" represent the cumulative points of maintenance performed by the user on their clothing after purchase. 【0075】 Each field in the column named "Favorite Score" will have a Favorite Score registered. The Favorite Score is a numerical representation of the overall degree of liking for an item, calculated based on the specified Favorite Score, the number of times the item has been worn (B), the time elapsed since the item was purchased (m), the care points, classification 1 and classification 2, and the "weighting table" shown in Figure 3(B). Details on how the management program 35 calculates the Favorite Score are explained in step S93 of the disposal decision process (see Figure 6). 【0076】 The calculation and registration of the favorite score may be performed daily, when there are changes to the registration information such as the number of times the item has been worn, or immediately before deciding whether or not to suggest (notify) the disposal of the clothing. 【0077】 Each field in the column named "Favorite Ranking" registers the ranking of the clothing item based on its favorite score. For example, the clothing item with the highest favorite score will be ranked "1". The determination and registration of the "Favorite Ranking" by management program 35 is performed together with the calculation and registration of the favorite score. The determination of the "Favorite Ranking" by management program 35 is an example of "performing ranking on managed items". 【0078】 Each field in the column named "Photo Data" contains photo data of the clothing. The user takes pictures of the clothing using camera 25. Application 27 sends the image data generated by camera 25, along with the purchase date of the clothing, to the management server 30. Management program 35 registers the photo data of the clothing, along with the purchase date, into the clothing management database. 【0079】 The column named "Decision Date" has two sub-columns named "1st" and "2nd". 【0080】 The fields in the two sub-columns, named "Decision Date 1" and "Decision Date 2," each register the decision date on which a decision is made regarding whether or not to notify the disposal of the item. The decision date is determined by the management program 35 based on the "Category 2" of clothing such as spring items, the "Purchase Date" of the clothing, and the decision date correspondence table shown in Figure 3(C). Further details are explained in the decision correspondence table. 【0081】 Each field in the column named "Judged Flag" is registered with either a "1" flag indicating that a discard decision or discard notification has already been made for the clothing, or a "0" flag indicating that a discard decision or discard notification has not yet been made for the clothing. The initial value of the "Judged Flag" is "0". The management program 35 updates the "Judged Flag" from "0" to "1" for clothing that has been judged for discard. The decision of whether or not to discard clothing is performed only for clothing with a "0" judged flag registered, and not for clothing with a "1" judged flag registered. In other words, once a clothing item has been judged for discard, the decision of whether or not to discard it is not performed again. 【0082】 Each field in the column named "Disposal Confirmation Flag" will be registered with either "1" to indicate that the clothing has been disposed of, or "0" to indicate that the clothing has not been disposed of. The initial value of the "Disposal Confirmation Flag" is "0". When a user disposes of clothing, they use application 27 to input information indicating that the clothing has been disposed of into the user terminal 20. When the management program 35 receives information indicating that the clothing has been disposed of from the user terminal 20, it updates the disposal confirmation flag from "0" to "1". The decision of whether or not to dispose of clothing is made only for clothing with a disposal confirmation flag of "0" registered, and not for clothing with a discarded confirmation flag of "1" registered. The management program 35 will either prohibit updating the data (information) for records with a discarded confirmation flag of "1" registered, or delete the record. For example, if a user wishes to keep information such as photos of clothing they previously owned, records with a disposal confirmation flag of "1" will remain and will not be deleted. 【0083】 Furthermore, even if a user has been notified to discard an item of clothing, the user may not have actually discarded it. Conversely, even if a user has not been notified to discard an item of clothing, the user may have actually discarded it. In other words, the value of the "determined" flag and the value of the "discarded" flag are not necessarily correlated. 【0084】 [Care scoring table] The care scoring table shown in Figure 3(A) is a table for quantifying the care that users have taken on their clothing. 【0085】 The maintenance scoring table includes a column named "Maintenance Name" and a column named "Score". 【0086】 Each field in the column named "Care Name" contains the name of a care method, such as "Washing," "Washing with Fabric Softener," "Delicate Wash," "Steam Ironing," and "Dry Cleaning." Each field in the column named "Points" contains the points assigned to each care method, such as "Washing." In short, the care scoring table is a table that associates the type of care with the points assigned to it. 【0087】 [Weighted Table] The weighting table shown in Figure 3(B) is used to adjust the target unit price per wear (see Figure 2(A)) according to the type of clothing, such as "everyday wear" or "fashionable wear." 【0088】 The weighting table includes a column named "Classification 1" and a column named "Weight Coefficient". 【0089】 Each field in the column named "Classification 1" registers the type of clothing (Classification 1), which is one of the following: "Stylish Clothes," "Everyday Clothes," or "Loungewear." Each field in the column named "Weight Coefficient" registers the weight coefficient corresponding to each type of clothing. In other words, the weighting table is a table that associates the types of clothing in Classification 1 with the weight coefficients. 【0090】 In this embodiment, the clothing type "fashionable clothing" is associated with a weight coefficient of "1.2". The clothing type "everyday clothing" is associated with a weight coefficient of "1.0". The clothing type "loungewear" is associated with a weight coefficient of "0.8". By correcting the target unit price per wear (threshold unit price), which is a threshold, using the weight coefficient, expensive "fashionable clothing" becomes less likely to be discarded compared to "everyday clothing" and "loungewear", while "loungewear" becomes more likely to be discarded compared to "everyday clothing" and "fashionable clothing". Clothing types "fashionable clothing", "everyday clothing", and "loungewear" are examples of category information. 【0091】 [Decision Date Correspondence Table] The decision date correspondence table shown in Figure 3(C) is a table used to determine the decision date for each garment. 【0092】 The decision date correspondence table has three columns labeled "Classification 2," "First Decision Date," and "Second Decision Date." 【0093】 Each field in the column labeled "Classification 2" contains one of the following: "Summer items," "Autumn items," "Winter items," "Spring items," or "Year-round items." Each field in the column labeled "First Decision Date" and each field in the column labeled "Second Decision Date" contains one of the following dates: "4 / 1," "7 / 1," "10 / 1," or "1 / 7," or one of the following functions: "First Function" or "Second Function." The dates are associated with "Summer items," "Autumn items," "Winter items," and "Spring items." The "First Function" and "Second Function" are associated with "Year-round items." 【0094】 The "spring" clothing category is generally used from mid-March to mid-June. The "summer" clothing category is generally used from mid-June to mid-September. The "autumn" clothing category is generally used from mid-September to mid-December. The "winter" clothing category is generally used from mid-December to mid-March. The periods for which each type of clothing is used are examples of estimated usage periods. 【0095】 The clothing category "Spring Clothing" is associated with a first decision date of 1 / 7 (January 7th), which is before the estimated usage period, and a second decision date of 7 / 1 (July 1st), which is after the estimated usage period. The first decision date is the day when both the decision on whether or not to notify the disposal of the clothing and the calculation of the above-mentioned favorite score are made. The second decision date is the day when only the decision on whether or not to notify the disposal of the clothing is made. 【0096】 Similarly, the clothing type "Summer" is associated with April 1st (4 / 1), a date before the estimated usage period, as the first decision date, and October 1st (10 / 1), a date after the estimated usage period, as the second decision date. The clothing type "Autumn" is associated with July 1st (7 / 1), a date before the estimated usage period, as the first decision date, and January 7th (1 / 7), a date after the estimated usage period, as the second decision date. The clothing type "Winter" is associated with October 1st (10 / 1), a date before the estimated usage period, as the first decision date, and April 1st (4 / 1), a date after the estimated usage period, as the second decision date. Note that if the favorite score is calculated regularly, such as daily, the first and second decision dates do not need to be distinguished. Furthermore, even if the decision on whether or not to notify the customer of the disposal of clothing and the calculation of the above-mentioned favorite score are both made on both the first and second decision days, the first and second decision days do not need to be distinguished. 【0097】 The clothing type "all-season" is associated with the first function as the first decision date and with the second function as the second decision date. The first function takes the purchase date of the clothing as an argument and returns the date that is closest to January 7, April 1, July 1, or October 1, after a predetermined period (e.g., one year) has elapsed since the purchase date. The second function takes the date (return value) output by the first function as an argument and returns the date that is closest to January 7, April 1, July 1, or October 1, after six months have elapsed since that date. In other words, for all-season clothing, a decision on whether or not to notify disposal is made every six months starting one year after the purchase date. 【0098】 The management program 35 determines and identifies the first and second decision dates based on the type of clothing (classification 2) and purchase date registered in the clothing management database and the decision date correspondence table, and registers the determined first and second decision dates in the respective fields of the column named "Decision Date" in the clothing management database. 【0099】 [Operation (processing) of the clothing management system 10] The user terminal 20 and the management server 30 perform the following processes: registering information about the user and clothing in the management database (see Figure 4), registering maintenance information, which is information about wearing and caring for the clothing, in the management database (see Figure 5), and determining which clothing items the user should be notified to discard (see Figures 6 and 7). 【0100】 Furthermore, the processes executed by the user terminal 20 are processes executed by the CPU 21 of the user terminal 20, and are processes that the application 27 causes the CPU 21 to execute. Also, the processes executed by the management server 30 are processes executed by the CPU 31, and are processes that the management program 35 causes the CPU 31 to execute. In addition, in the flowcharts shown in Figures 4 to 7, the database is abbreviated as "DB". 【0101】 The user terminal 20 and the management server 30 execute the processes shown in Figure 4 to register information about the user and clothing in the management database. 【0102】 The user downloads the application 27 from a website to the user terminal 20 (S11) and launches the downloaded application 27 (S12). The launched application 27 displays a main screen (not shown) on the touch panel 24 (S13). The main screen has multiple screen selection icons that accept screen selection by the user. The screen selection icons include an icon to specify the user registration screen (see Figure 8(A)), an icon to specify the clothing registration screen (see Figures 8(B) and 9(A)), an icon to specify the first clothing selection screen (see Figure 9(B)), an icon to specify the weight registration screen (not shown), an icon to specify the first disposal registration screen (not shown), an icon to specify the second disposal registration screen (not shown), and an icon to specify the first maintenance information registration screen (not shown). Alternatively, the main screen may have pull-down menus or tabs with multiple options to specify each of the above screens instead of these icons. The user selects a screen by selecting an icon, pull-down menu, or tab. 【0103】 On the main screen, the user selects an icon that specifies the user registration screen (see Figure 8(A)) (S14). 【0104】 Based on the selection of an icon that specifies the user registration screen (S14), application 27 displays the user registration screen (see Figure 8(A)) on the touch panel 24 (S15). Since user registration is mandatory, application 27 may display the user registration screen on the touch panel 24 without displaying the main screen. Furthermore, after user registration is complete, application 27 does not need to display the icon that specifies the user registration screen (see Figure 8(A)) on the main screen. 【0105】 The user registration screen shown in Figure 8(A) is a screen for registering a user by receiving user information, which is information about the user. The user registration screen has the words "Please enter your name, etc." and text boxes 41 and 42 for receiving the user's name. The user registration screen also has a pull-down menu 43 for receiving the user's gender, a pull-down menu 44 for receiving the user's age, a pull-down menu 45 for receiving the user's weight, a pull-down menu 46 for receiving the target cost per wear, and a "Register" icon 47. The pull-down menu 46 has multiple options, for example, from 50 yen to 1000 yen in 50 yen increments. If the user does not specify (select) a target cost per wear, the app 27 will determine a predetermined amount, such as 500 yen, as the target cost per wear. 【0106】 The user enters their name, selects their gender, age, weight, and target cost per wear, and then selects the "Register" icon 47. 【0107】 As shown in Figure 4, the user terminal 20 accepts the user's input of their name and other information, and the selection of the "Register" icon 47 (S16). The user terminal 20 sends an HTTP request containing the user information, such as the user's name, and the registration request to the management server 30 via the communication interface 23 and the internet 11 (S17). The "requests" described below, such as the registration request, are, for example, commands. The communication address of the management server 30 is held by the downloaded application 27 and stored in the terminal memory 22. 【0108】 The management server 30 receives an HTTP request containing user information through the communication interface 33 (S17). The management server 30 generates a new user ID in accordance with the registration request and generates new records in the user management database and the clothing management database (S18). The management server 30 registers the newly generated user ID in the newly generated record (S18). The management server 30 also registers the user information obtained in step S17 in the newly generated record in the user management database (S18). 【0109】 The management server 30 sends back an HTTP response containing a registration completion notification with the newly generated user ID to the user terminal 20 via the communication interface 33 and the internet 11 as a response to the HTTP request received in step S17 (S19). 【0110】 The user terminal 20 receives an HTTP response containing a registration completion notification with a user ID via the communication interface 23 (S19). The user terminal 20 stores the received user ID in the terminal memory 22 (S20). Although not shown in the flowchart, the user terminal 20 also displays a screen on the touch panel 24 indicating that registration is complete. 【0111】 Based on the fact that the user terminal 20 received the selection of an icon for the clothing registration screen (see Figures 8(B) and 9(A)) on the main screen displayed on the touch panel 24 in step S13 (S21), the user terminal 20 displays the clothing registration screen on the touch panel 24 (S22). 【0112】 The clothing registration screen shown in Figures 8(B) and 9(A) is a screen that accepts input of clothing information, which is information about the clothing owned by the user. As shown in Figure 8(B), the clothing registration screen has a pull-down menu 51 associated with the words "Please register clothing," the words "1st item," and the words "Purchase date," and a text box 52 associated with the word "Price." The clothing registration screen also has clothing icons 53, 54, and 55 associated with the word "Category." Clothing icon 53 has a shape that represents fashionable clothing and accepts the specification that the type of clothing to be registered is "fashionable clothing." Clothing icon 54 has a shape that represents everyday clothing and accepts the specification that the type of clothing to be registered is "everyday clothing." Clothing icon 55 has a shape that represents loungewear and accepts the specification that the type of clothing to be registered is "loungewear." 【0113】 The clothing registration screen also has a pull-down menu 56 associated with the word "Season." When the pull-down menu 56 is selected, the options "Spring," "Summer," "Autumn," "Winter," and "All Year Round" are displayed. The user specifies the type of clothing by selecting one of the displayed options. 【0114】 The garment registration screen shown in Figure 9(A) is displayed on the touch panel 24 by sliding the garment registration screen shown in Figure 8(B) downwards. As shown in Figure 9(A), the garment registration screen has a pull-down menu 57 associated with the words "Care Instructions". When the pull-down menu 57 is selected, options such as "Do not wet clean", "Do not iron at high temperature", and "Dry in the shade" are displayed. The user inputs the type of care instructions by selecting one of the displayed options. 【0115】 The clothing registration screen has a text box 58 associated with the words "Weight at Purchase". The user enters their weight at the time of purchase of the clothing being registered into the text box 58. Note that if clothing information is registered immediately after purchase, the weight at purchase will be the user's current weight. If clothing information for previously purchased clothing is registered after downloading app 27, the weight at purchase may be the estimated weight at the time the user purchased the clothing. 【0116】 The clothing registration screen has a pull-down menu 59 associated with the words "Favorite Rating". When the pull-down menu 59 is selected, the options "1", "2", "3", "4", and "5" are displayed. The user selects their subjective favorite rating for the clothing being registered from the displayed options. The selection of the specified favorite rating is accepted both when registering the clothing and on the first decision day when the decision to discard the clothing is made. Note that the favorite rating is not limited to 5 levels; any level of 2 or higher is acceptable. 【0117】 The clothing registration screen has a pull-down menu 60 associated with the words "Hanger Number". If the hanger on which the registered clothing is hung has a number, the user selects that number. If the hanger on which the registered clothing is hung does not have a number, the user does not need to enter a hanger number. In other words, specifying a hanger number is optional. 【0118】 The clothing registration screen has a camera icon 61 associated with the words "Camera Shooting". When the camera icon 61 is selected, application 27 launches an unillustrated camera application that controls the operation of camera 25 via OS 26. The launched camera application causes camera 25 to take an image of the clothing according to the user's imaging instructions and generates image data. Application 27 acquires the image data generated by camera 25 and the camera application as clothing image data. 【0119】 The clothing registration screen has an "Next Registration" icon 62 and a "Registration Complete" icon 63. The user selects the "Next Registration" icon 62 to continue registering the next clothing item. The user selects the "Registration Complete" icon 63 to finish registering clothing items. 【0120】 As shown in Figure 4, the user terminal 20 accepts input of clothing information on the clothing registration screen (S23). The user terminal 20 sends an HTTP request containing the user ID stored in the terminal memory 22 and the clothing information registration request to the management server 30 via the communication interface 23 and the internet 11 (S24). The process in step S23 is an example of the management information acquisition process. The process in step S24 is an example of the management information transmission process. 【0121】 The management server 30 receives an HTTP request containing a user ID and a clothing information registration request through the communication interface 33 (S24). The management server 30 identifies a record in the clothing management database that has the same user ID as the received user ID, and registers the clothing information in the identified record (S25). The process in step S25 is an example of the management information registration process. 【0122】 The management server 30 sends an HTTP response, including a registration completion notification, to the user terminal 20 via the communication interface 33 and the internet 11 as a response to the HTTP request received in step S24 (S26). 【0123】 The user terminal 20 receives an HTTP response, including a registration completion notification, through the communication interface 23 (S26). Based on the receipt of the registration completion notification, the user terminal 20 displays a registration completion notification screen (not shown) on the touch panel 24 (S27). 【0124】 If the user wants to select the clothes to wear today through app 27, they select the icon that specifies the first clothing selection screen on the main screen displayed in step S13 (S28). 【0125】 Based on the user's instruction to select a screen (S28), the user terminal 20 displays the first clothing selection screen (see Figure 9(B)) on the touch panel 24 (S29). 【0126】 As shown in Figure 9(B), the first clothing selection screen has the words "Please specify conditions," clothing icons 53, 54, and 55 associated with the word "Category," a pull-down menu 56 associated with the word "Season," and an "OK" icon 64. When going out, the user selects either the clothing icon 53 indicating fashionable clothes or the clothing icon 54 indicating everyday clothes, and when staying at home, they select either the clothing icon 54 or the clothing icon 55 indicating loungewear. The user also selects the pull-down menu 56 and specifies the displayed options such as "Spring clothes." After specifying the type of clothing (category) and the season such as "Spring clothes," the user selects the "OK" icon 64. 【0127】 As shown in Figure 4, the user terminal 20, based on receiving user input such as the type of clothing (S30), sends an HTTP request including the user ID and a clothing information request with specified information to the management server 30 via the communication interface 23 and the internet 11 (S31). The specified information is information indicating the type of clothing and the season. 【0128】 The management server 30 receives an HTTP request containing a user ID and a request for clothing information through the communication interface 33 (S31). Based on the received user ID and specified information, the management server 30 identifies the record (clothing) in the clothing management database and obtains data containing information such as clothing ID, image data, and hanger number from the identified record as reply data (S32). The image data may be so-called thumbnail image data generated by reducing the resolution of photographic image data generated by imaging the clothing, or it may be both photographic image data and said thumbnail image data. 【0129】 The management server 30 sends an HTTP response containing reply data to the user terminal 20 via the communication interface 33 and the internet 11 as a response to the HTTP request received in step S28 (S33). The reply data is, for example, HTML data including JavaScript, clothing ID, and image data. 【0130】 The user terminal 20 receives an HTTP response containing reply data through the communication interface 23 (S33). The user terminal 20 displays a second clothing selection screen (see Figure 10(A)) on the touch panel 24, which has an image indicated by the image data contained in the received reply data (S34). 【0131】 As shown in Figure 10(A), the second clothing selection screen includes text such as "Summer Clothes" indicating the season specified by the user, and multiple clothing selection icons 65. The clothing selection icons 65 are icons that have images (thumbnail images) indicated by the image data included in the reply data. The user selects a clothing selection icon 65 if they want to see detailed information about the clothing. 【0132】 As shown in Figure 4, the user terminal 20, based on the user's selection of the clothing specification icon 65 (S35), displays the clothing details screen (see Figure 10(B)) on the touch panel 24 (S36). 【0133】 As shown in Figure 10(B), the clothing details screen includes the words "Stylish Clothes" and "Summer Clothes," a clothing image 66, text indicating information about the clothing, a "Back" icon 67, a "Wear" icon 68, and an "Exit" icon 69. The information about the clothing includes the hanger number on which the clothing is hanging, the date the clothing was purchased, the purchase price of the clothing, the number of times the clothing has been worn to date, care instructions, the user's weight at the time of purchase, and the user's level of preference for the clothing. 【0134】 The user selects the "Wear" icon 68 to wear the selected clothing. The user selects the "Back" icon 67 to return to the second clothing selection screen (see Figure 10(A)) which shows a list of summer clothing. The user selects the "Exit" icon 69 to close the app 27 or to display another screen such as the main screen (not shown). 【0135】 As shown in Figure 4, the user terminal 20 accepts the user's selection of an icon on the clothing details screen (S37). When the user terminal 20 determines that the icon selected by the user is the "back" icon 67 (S38: back), it displays the second clothing selection screen (see Figure 10(A)) again on the touch panel 24 (S34). Although not shown in the flowchart, when the user terminal 20 determines that the icon selected by the user is the "end" icon 69, it terminates the process or displays another screen, such as the main screen, on the touch panel 24. 【0136】 When the user terminal 20 determines that the icon selected by the user on the clothing details screen is the "Wear" icon 68 (S38: Wear), it sends an HTTP request including the user ID and a wear registration request with the clothing ID to the management server 30 via the first communication interface 23 and the internet 11 (S39). 【0137】 The management server 30 receives an HTTP request containing a user ID and a clothing ID, along with a wear registration request, through the second communication interface 33 (S39). The management server 30 identifies a record in the clothing management database that matches the received user ID and clothing ID, and adds "1" to the wear count B of the identified record (S40). The management server 30 also calculates and updates the "wear unit price," "favorite score," and "favorite ranking," which change in accordance with the update of the wear count (S40). 【0138】 Although not shown in the flowchart, based on the update of the clothing management database (S40), the management server 30 sends an HTTP response containing an update completion notification to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S39. Upon receiving the HTTP response, the user terminal 20 terminates the process or displays another screen, such as the main screen, on the touch panel 24. 【0139】 If the user wants to register their current weight (latest weight), in step S13, they select the icon that specifies the weight registration screen on the main screen displayed on the touch panel 24 (S41). 【0140】 Based on the user's selection of an icon to specify the weight registration screen (S41), the user terminal 20 displays a weight registration screen (not shown) on the touch panel 24 (S42). The weight registration screen has a text box for entering weight or a pull-down menu for selecting weight, and a "Register" icon. After entering weight on the weight registration screen, the user selects the "Register" icon (S43). 【0141】 Based on the user terminal 20's acceptance of the selection of the "Register" icon (S43), it sends an HTTP request containing the user ID and a registration request with the weight (latest weight) to the management server 30 via the first communication interface 23 and the internet 11 (S44). The processing in step S44 is an example of the latest weight transmission process. 【0142】 The management server 30 receives an HTTP request containing a user ID and a registration request with weight information via the second communication interface 33 (S44). The management server 30 identifies a record in the user management database that has the same user ID as the received user ID, and overwrites the "latest weight" of the identified record with the received weight (S45). 【0143】 Although not shown in the flowchart, based on the update of the user management database, the management server 30 sends an HTTP response containing an update completion notification to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S44. Upon receiving this HTTP response, the user terminal 20 terminates the process or displays another screen, such as the main screen, on the touch panel 24. 【0144】 If the user disposes of clothing in accordance with the notification from app 27 described below (see Figure 7, step S115), in step S13, the user selects the icon to specify the first disposal registration screen on the main screen displayed on the touch panel 24 (S46). 【0145】 Based on the user's selection of an icon to indicate the first disposal registration screen (S46), the user terminal 20 displays the first disposal registration screen (not shown) on the touch panel 24 (S47). The first disposal registration screen is similar to the first clothing selection screen (see Figure 9(B)) and accepts the specification of the clothing category and season. After specifying the clothing category (type) and season on the first disposal registration screen, the user selects the "OK" icon (not shown) (S48). 【0146】 The user terminal 20 accepts the specification of the clothing category (type) and season on the first disposal registration screen (S48). The user terminal 20 sends an HTTP request including the user ID and clothing information request to the management server 30 via the first communication interface 23 and the internet 11 (S49). The clothing information request contains specification information indicating the clothing category (type) and season. The specification information may also include information indicating that it is limited to clothing for which disposal has been notified. 【0147】 The management server 30 receives an HTTP request containing the user ID and clothing information request through the second communication interface 33 (S49). The management server 30 identifies the record (clothing) indicated by the received user ID and specified information in the clothing management database and retrieves the data registered in the identified record (S50). The management server 30 sends an HTTP response containing the retrieved data (reply data) back to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S49 (S51). The reply data is, for example, HTML data. 【0148】 The user terminal 20 receives reply data through the first communication interface 23 (S51). The user terminal 20 displays a second disposal registration screen (not shown) on the touch panel 24, which is indicated by the received reply data (S52). The second disposal registration screen is similar to the second clothing selection screen (see Figure 10(A)), and has multiple clothing selection icons, allowing the user to select clothing. On the second disposal registration screen, the user selects a clothing selection icon that indicates the clothing to be disposed of (S53). 【0149】 The user terminal 20 accepts the selection of a clothing designation icon indicating discarded clothing (S53). The user terminal 20 sends an HTTP request to the management server 30 via the first communication interface 23 and the internet 11, containing a registration request with a clothing ID indicating the selected clothing and a user ID (S54). 【0150】 The management server 30 receives an HTTP request containing a user ID and a clothing ID, along with a registration request, through the second communication interface 33 (S54). The management server 30 identifies a record (clothing) in the clothing management database that has the same user ID and clothing ID as the received record, and overwrites the discard confirmation flag of "0" in the identified record to "1" (S55). 【0151】 Although not shown in the flowchart, based on the update of the clothing management database, the management server 30 sends an HTTP response, including an update completion notification, to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S54. Upon receiving this HTTP response, the user terminal 20 terminates the process or displays another screen, such as the main screen, on the touch panel 24. 【0152】 The user inputs a termination command to the user terminal 20 by, for example, selecting "×" shown on the display screen of application 27 (S56). Based on the input of the termination command (S56), the user terminal 20 terminates the process (end). 【0153】 Next, the process of registering that clothing has been worn or maintained after it has been worn will be explained with reference to Figure 5. 【0154】 On the main screen displayed on the touch panel 24 (S13), the user selects an icon to specify the first maintenance information registration screen (S60), and displays the first maintenance information registration screen (not shown) on the touch panel 24 (S61). The first maintenance information registration screen is a screen similar to the first clothing selection screen (see Figure 9(B)), and accepts the specification of clothing category and season. After specifying the clothing category (type) and season on the first maintenance information registration screen, the user selects the "OK" icon (not shown) (S62). 【0155】 The user terminal 20 accepts the specification of the clothing category (type) and season on the first maintenance information registration screen (S62). The user terminal 20 sends an HTTP request including the user ID and clothing information request to the management server 30 via the first communication interface 23 and the internet 11 (S63). The clothing information request contains specification information indicating the clothing category (type) and season. 【0156】 The management server 30 receives an HTTP request containing the user ID and clothing information request through the second communication interface 33 (S63). The management server 30 identifies the record indicated by the received user ID and specified information in the clothing management database and retrieves the data registered in the identified record (S64). The management server 30 sends an HTTP response containing reply data generated from the retrieved data back to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S63 (S65). The reply data is, for example, HTML data. 【0157】 The user terminal 20 receives an HTTP response containing reply data via the first communication interface 23 (S65). The user terminal 20 displays a second maintenance information registration screen (not shown) on the touch panel 24, which is indicated by the received reply data (S66). The second maintenance information registration screen is similar to the second clothing selection screen (see Figure 10(A)) and has multiple clothing selection icons. On the second maintenance information registration screen, the user selects a clothing selection icon that indicates the clothing that has been worn or maintained (S67). 【0158】 The user terminal 20 accepts the selection of a clothing designation icon indicating clothing that has been worn or maintained (S67). The user terminal 20 displays a third maintenance information registration screen (see Figure 11) for the clothing indicated by the selected clothing designation icon on the touch panel 24 (S68). 【0159】 As shown in Figure 11(A), the third maintenance information registration screen includes the text "Stylish clothing, Spring items" indicating the type of clothing, the text "Hanger number: 02" indicating the hanger number on which the clothing is hanging, and a clothing image 66 showing an image of the clothing. The user confirms that the clothing for which maintenance information is to be registered is the specified clothing by looking at the hanger number and clothing image. 【0160】 The third maintenance information registration screen has a radio button 71 associated with the word "wear" and a radio button 72 associated with the word "care". When the user registers wearing the clothing, they select radio button 71. When the user registers maintenance on the clothing, they select radio button 72. When the user registers both wearing and maintenance on the clothing, they select radio buttons 71 and 72. Note that "care" and "maintenance" have the same meaning. 【0161】 The third maintenance information registration screen has multiple checkboxes 73-83, each corresponding to a word indicating the name of the maintenance item. Checkbox 73 corresponds to the word "Washing," checkbox 74 corresponds to the word "Fabric softener," checkbox 75 corresponds to the word "Delicate wash," and checkbox 76 corresponds to the word "Hand wash." Additionally, checkbox 77 corresponds to the word "Steam ironing," checkbox 78 corresponds to the word "Brushing," checkbox 79 corresponds to the word "Stain removal," and checkbox 80 corresponds to the word "Repair (buttons / fraying)." Furthermore, checkbox 81 corresponds to the word "Dry cleaning," checkbox 82 corresponds to the word "Disinfectant / deodorizing / odor-removing spray," and checkbox 83 corresponds to the word "Pilling remover." Figure 11(B) is a screen displayed on the touch panel 24 by sliding the third maintenance information registration screen shown in Figure 11(A), and is a part of the third maintenance information registration screen. 【0162】 The user selects a checkbox corresponding to the type of care they performed on the clothing. 【0163】 The third maintenance information registration screen has an "OK" icon 84. The user selects checkboxes 73-83 and then selects the "OK" icon 84. 【0164】 As shown in Figure 5, the user terminal 20 accepts the selection of checkboxes 73-83 and the "OK" icon 84 on the third maintenance information registration screen (S69). The user terminal 20 sends an HTTP request including the user ID and registration request to the management server 30 via the first communication interface and the internet 11 (S70). The registration request includes the clothing ID and maintenance information. The clothing ID is the clothing ID of the clothing specified by the user on the first maintenance information registration screen. The maintenance information corresponds to the radio buttons 71, 72 and checkboxes 73-83, and includes information indicating whether the user has worn the clothing and information indicating the type of care the user has performed on the clothing. The maintenance information is an example of usage information. 【0165】 The management server 30 receives an HTTP request containing the user ID and registration request through the second communication interface 33 (S70). 【0166】 The management server 30 calculates maintenance points based on the received maintenance information (S71). More specifically, the management server 30 uses the information indicated in the maintenance information, which is the name of the maintenance performed by the user on the clothing, and the maintenance point table (see Figure 3(A)) to assign points to each maintenance performed by the user on the clothing. The management server 30 calculates the maintenance points by adding up all the points. For example, if a delicate garment identified by clothing ID "002" has undergone "delicate washing" and "repair," a total of 5 points (2 points for delicate washing and 3 points for repair) is calculated in association with clothing ID "002" (S71). 【0167】 The management server 30 identifies a record in the clothing management database that has a user ID and clothing ID that match the user ID and clothing ID received in step S70 (S72). If the maintenance information received in step S70 indicates that the clothing has been worn in the identified record, the management server 30 adds "1" to "Number of Wears B" (S73). The management server 30 also adds the care points calculated in step S71 to "Care Points" in the identified record (S73). 【0168】 The management server 30 calculates the favorite score (S74) based on the data registered in the record identified in step S72. More specifically, the favorite score is calculated using the following formula. 【0169】 Favorite Score = [Number of Wears B] × [Weighting Coefficient] × A / [365 days × Elapsed Time m] + "Care Points" / [Number of Wears B] + [Latest Designated Favorite Score] / [First Designated Favorite Score] 【0170】 The weight coefficient is a coefficient determined by the type of clothing, and is determined by the type of clothing and the weighting table (see Figure 3(B)). Specifically, a weight coefficient of "1.2" is determined for "fashionable clothing," a weight coefficient of "1.0" is determined for "everyday clothing," and a weight coefficient of "0.8" is determined for "loungewear." 【0171】 "A" is a value corresponding to "Spring items" and "Year-round items" in Category 2. A=4 (number of seasons) is set for "Spring items," "Summer items," "Autumn items," and "Winter items," and A=1 is set for "Year-round items." In other words, "A" is a correction value that compensates for the difference in usage period over a year between "Spring items," "Summer items," "Autumn items," and "Winter items" and "Year-round items." 【0172】 In the above calculation formula, the value obtained by dividing [Number of Wears B] × "A" by [365 days × Elapsed Time m] indicates the frequency of wearing the clothing from the date of purchase to the mth year (where m is an integer greater than or equal to 1). 【0173】 In the above calculation formula, the value obtained by dividing "Care Points" by [Number of Wears B] indicates the degree of care (frequency of maintenance) per wear. In other words, this value indicates how much effort the user puts into their clothing. 【0174】 In the above calculation formula, the value obtained by dividing [Latest Favorite Rating] by [Initial Favorite Rating] represents the user's subjective favorite rating and the degree to which that favorite rating has changed. 【0175】 Thus, the "favorite score" is a numerical value that indicates the overall level of preference, taking into account factors such as how often the clothing is worn, the type of clothing, the degree of care taken, and the user's subjective opinion. 【0176】 In the record identified by clothing ID "002" in Figure 2(B), the number of times worn B=12, the elapsed time m=2, the weight coefficient corresponding to fashionable clothing of category 1 is 1.2, the care points=41, the initial designated favorite rating=5, and the latest designated favorite rating=5, so the favorite rating score = 12 × 1.2 × 4 / (365 × 2) + 41 / 12 + 5 / 5 = 4.4. 【0177】 The server memory pre-stores the function that performs the above calculation. The management program 35 passes the updated wear count B and other data registered in the record identified in step S72 as arguments to the above function and receives the favorite score as the return value (S74). 【0178】 The management server 30 overwrites the "favorite score" of the record identified in step S72 with the favorite score calculated in step S74 (S75). The management server 30 also updates the "favorite ranking" based on the updated favorite score (S76). 【0179】 In response to the HTTP request received in step S70, the management server 30 sends an HTTP response, including a registration completion notification, back to the user terminal 20 via the second communication interface 33 and the internet 11 (S77). 【0180】 The user terminal 20 receives an HTTP response, including a registration completion notification, through the first communication interface 23 (S77). Based on the receipt of the registration completion notification, the user terminal 20 displays a registration completion screen (not shown) on the touch panel 24 (S78). The user inputs a termination command to the user terminal 20, for example, by selecting "×" shown on the display screen of the application 27 (S56). Based on the input of the termination command (S56), the user terminal 20 terminates the process (end). 【0181】 Next, the process of determining when to discard clothing and notifying the user will be explained with reference to Figures 6 and 7. 【0182】 The user terminal 20 (application 27) determines whether today's date is one of the first, second, third, or fourth predetermined dates pre-stored in the terminal memory 22 (S81). The first predetermined date is January 7th, the second predetermined date is April 1st, the third predetermined date is July 1st, and the fourth predetermined date is October 1st. If the user terminal 20 determines that today's date is not one of the first to fourth predetermined dates (S81: No), it terminates the process (end). 【0183】 If the user terminal 20 determines that today's date is one of the four predetermined dates (S81: Yes), it displays a notification screen on the touch panel 24 corresponding to the predetermined date (S82). Specifically, if the user terminal 20 determines that today's date is either the first predetermined date (January 7th) or the third predetermined date (July 1st), it displays the first notification screen (see Figure 12(A)) on the touch panel 24. If the user terminal 20 determines that today's date is either the second predetermined date (April 1st) or the fourth predetermined date (October 1st), it displays the second notification screen (not shown) on the touch panel 24. 【0184】 As shown in Figure 12(A), the first notification screen has the text "Do you want to organize (dispose of) spring, autumn, and year-round clothing?", a checkbox 91 corresponding to the text "Spring clothes", a checkbox 92 corresponding to the text "Autumn clothes", a checkbox 93 corresponding to the text "Year-round clothes", a radio button 94 corresponding to the text "Do not organize (dispose of)", and an "OK" icon 90. 【0185】 The user selects checkboxes 91, 92, and 93 according to the type of clothing to be sorted (discarded), or selects radio button 94 if they do not want to sort any clothing, and then selects the "OK" icon 90. 【0186】 The second notification screen is the same as the first notification screen, and includes the text "Do you want to organize (dispose of) your summer, winter, and year-round clothing?", a checkbox associated with the text "Summer clothing", a checkbox associated with the text "Winter clothing", a checkbox associated with the text "Year-round clothing", a radio button associated with the text "Do not organize (dispose of)", and an "OK" icon. 【0187】 As shown in Figure 6, the user terminal 20 accepts the user's selection of checkboxes 91-93 or radio buttons 94 and the "OK" icon 90 (S83). The user terminal 20 determines whether radio button 94 has been selected, that is, whether or not to suggest discarding the clothing (S84). If the user terminal 20 determines that radio button 94 has been selected and does not want to suggest discarding the clothing (S84: No), it terminates the process (end). 【0188】 If the user terminal 20 determines that one or all of the checkboxes 91, 92, and 93 have been selected and that it is appropriate to propose the disposal of clothing (S84: Yes), it sends an HTTP request including the user ID and a request for clothing information, etc., to the management server 30 via the first communication interface 23 and the internet 11 (S85). The request for clothing information, etc., includes designation information indicating the type of checkbox selected by the user. The designation information may be, for example, information indicating one or all of "spring items," "autumn items," or "all-season items." 【0189】 The management server 30 receives an HTTP request containing the user ID and clothing information through the second communication interface 33 (S85). The management server 30 uses the received user ID and specified information to identify records in the clothing management database (S86). For example, if the specified information indicates all of "spring items," "autumn items," and "all-season items," the management server 30 identifies all records in which "spring items," "autumn items," and "all-season items" are registered under "Category 2." The management server 30 retrieves data from the identified records (S86). 【0190】 The management server 30 identifies the record from the records identified in step S86 that matches today's date and the first decision date (see Figure 2(A)) (S87). In other words, in step S87, the record from which the specified favorite rating (latest) should be obtained is identified. For example, if today's date is January 7th, spring clothing is identified as the clothing from which the specified favorite rating (latest) should be obtained. 【0191】 The management server 30 generates reply data based on the data obtained from the identified record, and sends the HTTP response containing the reply data back to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S85 (S88). The reply data is HTML data showing the decision execution screen (see Figure 12(B)). 【0192】 The user terminal 20 receives an HTTP response containing reply data through the first communication interface 23 (S88). The user terminal 20 displays the decision execution screen (see Figure 12(B)) indicated by the received reply data on the touch panel 24 (S89). 【0193】 As shown in Figure 12(B), the decision execution screen has the text, "Deciding which clothes to discard for spring, autumn, and year-round use. For spring clothes, please enter your current favorite rating," the word "Spring Clothes," and multiple clothing designation icons 65 and clothing images 66. The clothing designation icons 65 have images of spring clothes. When a clothing designation icon 65 is selected, a pull-down menu 59 (see Figure 9(A)) associated with the word "Favorite Rating" is displayed on the touch panel 24. The user selects the current (latest) favorite rating for spring clothes from "1" to "5". The clothing images 66 are simply images, not icons. For clothes purchased less than one year ago, the clothing image 66 is displayed instead of the clothing designation icon 65. In other words, for clothes purchased less than one year ago, it is not necessary to enter the current favorite rating. 【0194】 Although not shown in Figure 12(B), when the decision execution screen is slid, the words "Autumn items" and multiple clothing images 66 (see Figure 10(A)), the words "All-season items" and multiple clothing images 66, and an "OK" icon are displayed on the touch panel 24. 【0195】 The decision execution screen may also have a pull-down menu 45 (see Figure 8(A)) that accepts input of the current (latest) weight. 【0196】 After the user enters their rating of favorite items for spring clothing purchased more than a year ago, they select the unillustrated "OK" icon. 【0197】 As shown in Figure 6, the user terminal 20 accepts the input of the favorite rating and the selection of the "OK" icon (S90). The user terminal 20 sends an HTTP request containing the user ID and a decision execution request to the management server 30 via the first communication interface 23 and the internet 11 (S91). The decision execution request includes the favorite rating entered by the user. This favorite rating is associated with the clothing ID. 【0198】 The management server 30 receives an HTTP request containing the user ID and a decision execution request through the second communication interface 33 (S91). The management server 30 registers the favorite rating, weight, etc., included in the received decision execution request in the management database (S92). The management server 30 updates the favorite rating score and favorite rating ranking based on the registered favorite rating (S93). The management server 30 also uses the received user ID to obtain the user's "latest weight" and "target unit price" from the user management data (S94). The processing in step S93 is an example of the second calculation process. 【0199】 The management server 30 assigns sequential numbers starting from 1 to the multiple records identified in step S86, and retrieves the data registered in the first record (N=1) (S95). 【0200】 The management server 30 determines whether either the "judgmented flag" or the "disposal confirmation flag" of the acquired data is "1" (S96). In other words, in step S96, it is determined whether the clothing indicated by the record currently being judged is clothing that has already been judged to be disposed of, or clothing that has already been disposed of. 【0201】 If the management server 30 determines that either the "judgmented flag" or the "discard confirmation flag" of the acquired data is "1" (S96: Yes), it determines whether the current N is the final value (S97). In other words, in step S97, it is determined whether a discard decision has been made for all the records identified in step S86. 【0202】 If the management server 30 determines that the current N is not the final value (S97: No), it increments N (S98) and repeats the process in step S95. That is, a decision is made to discard the clothing indicated by the next record. 【0203】 In step S96, if the management server 30 determines that both the "determined flag" and the "disposal confirmation flag" are not "1" (S96: No), it determines whether the weight difference calculated by subtracting the weight at the time of purchase obtained in step S95 from the latest weight obtained in step S94 is greater than or equal to a threshold weight pre-stored in the server memory 32 (S99). In other words, in step S99, it is determined whether the user's body shape has changed to the extent that it would be difficult to wear the clothing indicated by the record being judged. Note that multiple threshold weights corresponding to the type of clothing may be stored in the server memory 32. For example, a threshold weight of "3kg" is set for "fashionable clothes" and "everyday clothes," and a threshold weight of "4kg" is set for "loungewear." The processing in step S99 is an example of the second judgment process. 【0204】 If the management server 30 determines that the difference between the latest weight and the weight at the time of purchase is greater than or equal to a threshold weight (S99: Yes), it sends an HTTP response containing the inquiry data to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP request received in step S91 (S100). The inquiry data is HTML data showing a diet inquiry screen (not shown). 【0205】 The user terminal 20 receives an HTTP response containing the inquiry data through the first communication interface 23 (S100). The user terminal 20 displays the diet inquiry screen indicated by the received inquiry data on the touch panel 24 (S101). The diet inquiry screen has, for example, the text "Do you plan to go on a diet?" and "Yes" and "No" icons. The user selects either the "Yes" or "No" icon (S102). 【0206】 The user terminal 20 accepts the selection of either the "yes" or "no" icon (S102). The user terminal 20 sends an HTTP request containing the user ID and response information to the management server 30 via the first communication interface 23 and the internet 11 (S103). The response information is, for example, data "1" indicating that the "yes" icon was selected, or "0" indicating that the "no" icon was selected. 【0207】 The management server 30 receives an HTTP request containing the user ID and response information through the second communication interface 33 (S103). The management server 30 determines whether the received response information indicates that the user is going on a diet (S104). If the management server 30 determines that the received response information does not indicate that the user is going on a diet (S104: No), it registers a "1" flag as determined in the record being judged in the clothing management database (S105). After executing the process in step S105, the management server 30 executes the processes from step S97 onwards. 【0208】 If the management server 30 determines that the received response information indicates that the user will go on a diet (S104: Yes), or if it determines in step S99 that the difference between the current weight and the weight at the time of purchase is not greater than or equal to the threshold weight (S99: No), it calculates the threshold unit price (S106). The threshold unit price is the value obtained by multiplying the target unit price obtained in step S94 by a weighting coefficient (see Figure 3(B)) corresponding to clothing classification 1 obtained in step S95. The process in step S106, which calculates the threshold unit price by multiplying the target unit price by a weighting coefficient, is an example of a correction process. 【0209】 As shown in Figure 7, the management server 30 determines whether the unit price per wear obtained in step S95 is less than the threshold unit price calculated in step S106 (S107). In other words, in step S107, it is determined whether the clothing indicated by the record being judged has been worn a number of times commensurate with the purchase price. The process in step S107 is an example of the first judgment process. 【0210】 If the management server 30 determines that the unit price per wear is below the threshold unit price (S107: Yes), it calculates the maintenance point index (S108). The maintenance point index is the value obtained by dividing the maintenance points acquired in step S95 by the number of wears B. In other words, the maintenance point index is a numerical representation of the frequency of maintenance. The process in step S108 is an example of the first calculation process. 【0211】 The management server 30 determines whether the calculated care point index is less than a first threshold index pre-stored in the server memory 32 (S109). The first threshold index is, for example, 1.5. In step S109, a decision is made on whether or not to discard the clothing based on the degree to which the user has taken care of it. The process in step S109 is an example of the third decision process. 【0212】 If the management server 30 determines that the care point index is below the first threshold index (S109:Yes), it executes the process from step S105 onwards, which registers a "1" flag as determined. In other words, if an item of clothing has been worn a number of times commensurate with its purchase price (S107:Yes) and has not been cared for much (S109:Yes), it is determined to be an item of clothing for which disposal is suggested. 【0213】 If the management server 30 determines that the care point index is equal to or greater than the first threshold index (S109: No), it determines whether the "favorite ranking" obtained in step S95 is less than the threshold ranking (S110). The threshold ranking is, for example, the median number of clothing items owned by the user. The threshold ranking is the median number of clothing items belonging to the same category 2 (e.g., spring items) as the clothing item being judged. In other words, in step S110, it is determined whether the favorite ranking of the clothing item shown in the record being judged is within the top 50%. The threshold ranking may also be a fixed value such as "10". In that case, in step S110, it is determined whether the favorite ranking of the clothing item shown in the record being judged is within the top 10. The processing in steps S93 and S110 is an example of the fourth judgment process. 【0214】 If the management server 30 determines that the favorite ranking is not below the threshold ranking (S110: No), it executes the process from step S105 onwards, which registers a "1" flag as determined. In other words, if an item has been worn a number of times commensurate with its purchase price (S107: Yes) and has a low favorite ranking (S110: No), it is determined to be an item of clothing for which disposal is suggested. 【0215】 If the management server 30 determines that the favorite ranking is below the threshold ranking (S110:Yes), it executes the processes from step S97 onwards without executing the process in step S105, which registers a "1" judged flag. In other words, the clothing indicated by the record being judged is determined to be clothing that will not be suggested for disposal. Thus, even if clothing has been worn a number of times commensurate with the purchase price (S107:Yes), if it has been frequently cared for (S109:No) and has a high favorite ranking (S110:Yes), it is determined to be clothing that will not be suggested for disposal. 【0216】 In step S107, if the management server 30 determines that the unit price per wear is not below the threshold unit price (S107: No), it calculates a care point index (S108) and determines whether the calculated care point index is less than a second threshold index pre-stored in the server memory 32 (S111). The second threshold index is less than the first threshold index, for example, 1.2. In step S111, a decision to discard is made based on how often the user has taken care of the clothing. The process in step S111 is an example of the third decision process. 【0217】 If the management server 30 determines in step S111 that the care point index is not below the second threshold index (S111: No), it proceeds with the processing from step S97 onward without executing the process in step S105, which registers a "1" determined flag. In other words, the clothing indicated by the record being judged is determined to be clothing for which no disposal suggestion (notification) will be made. Thus, clothing that has not yet been worn a number of times commensurate with the purchase price (S107: No) and has been sufficiently cared for (S111: No) is determined to be clothing for which no disposal suggestion will be made. 【0218】 If the management server 30 determines in step S111 that the care point index is less than the second threshold index (S111:Yes), it determines in step S95 whether the elapsed period m obtained is less than the threshold period (S112). The threshold period is, for example, "3" years. If the management server 30 determines that the elapsed period m is less than the threshold period (S112:Yes), it executes the processes from step S97 onward without executing the process in step S105 which registers a "1" determined flag. In other words, the clothing indicated by the record being judged is determined to be clothing for which no disposal suggestion is made. Thus, clothing that has not yet been worn a number of times commensurate with the purchase price (S107:No), and has not been adequately cared for (S111:Yes), but has not been purchased more than 3 years ago (S112:Yes), is determined to be clothing for which no disposal suggestion is made. 【0219】 If the management server 30 determines in step S112 that the elapsed period m is not less than the threshold period (S112: No), it executes the processes from step S110 onward to determine whether the favorite ranking is below the threshold ranking. In this way, clothing that has not been worn a number of times commensurate with the purchase price (S107: No), has not been properly cared for (S111: Yes), and has been purchased more than three years ago (S112: No) is considered clothing that will not be suggested for disposal if it has a high favorite ranking, as described above. 【0220】 As shown in Figure 6, when the management server 30 determines in step S97 that N is the final value (S97: Yes), that is, when it determines that it has made a discard decision for all records, it retrieves the data for each record with the "1" determined flag registered (S113), as shown in Figure 7. Records with the "1" determined flag registered include not only records that were recently determined to be discarded, but also records that were determined to be discarded in the past. In other words, the management server 30 retrieves the data for all records that indicate clothing that has been determined to be discarded but has not yet been discarded. The clothing ID and other data retrieved by the management server 30 are an example of discard notification information. 【0221】 The management server 30 generates disposal notification data based on the acquired data (S114). The disposal notification data is HTML data showing the disposal suggestion screen (see Figure 13(A)) and the clothing confirmation screen (see Figure 13(B)). 【0222】 The management server 30 sends back an HTTP response containing the generated disposal notification data to the user terminal 20 via the second communication interface 33 and the internet 11 as a response to the HTTP response received in step S91 or step S103 (S115). Step S107: The process in step S115, which is executed after the process in Yes and step S105, is an example of the first disposal notification transmission process. Step S99: The process in step S115, which is executed after the process in step S105, is an example of the second disposal notification transmission process. 【0223】 The user terminal 20 receives an HTTP response containing disposal notification data via the first communication interface 23 (S115). The user terminal 20 displays the disposal suggestion screen (see Figure 13(A)) indicated by the received disposal notification data on the touch panel 24 (S116). The process in step S116 is an example of a display process. 【0224】 As shown in Figure 13(A), the disposal suggestion screen includes the text "Clothing recommended for disposal," the text "(Please check the clothing to be disposed of)," a clothing selection icon 65 and checkbox 95 associated with the text "Spring clothing," a clothing selection icon 65 and checkbox 95 associated with the text "Autumn clothing," and an "OK" icon 96. If the user wants to view details of the clothing suggested for disposal, they select the clothing selection icon 65. 【0225】 As shown in Figure 7, when the user terminal 20 receives the selection of the clothing selection icon 65 (S117), it displays the clothing confirmation screen (see Figure 13(B)) on the touch panel 24 (S118). 【0226】 As shown in Figure 13(B), the clothing confirmation screen includes text indicating the classification of clothing, such as "fashionable clothes" and "spring clothes," a clothing image 66, text indicating information about the clothing such as hanger number and purchase date, a "back" icon 97, and a "discard" icon 98. 【0227】 After reviewing the details of the clothing, the user selects the "Discard" icon 98 if they decide to discard it. If the user wants to review details of other clothing, they select the "Back" icon 97. The user then discards the clothing, for example, by selling it to a recycling shop or giving it to an acquaintance. 【0228】 As shown in Figure 7, the user terminal 20 accepts the selection of either the "Discard" icon 98 or the "Back" icon 97 (S119). The user terminal 20 determines whether the accepted icon is the "Discard" icon 98 or the "Back" icon 97 (S120). If the accepted icon is the "Discard" icon 98 (S120: Discard), the user terminal 20 decides to check the checkbox 95 associated with the corresponding clothing designation icon 65 (S121). If the accepted icon is the "Back" icon 97 (S120: Back), the user terminal 20 skips the process in step S121. 【0229】 The user terminal 20 displays a disposal suggestion screen (see Figure 13(A)) on the touch panel 24, with a checkbox 95 associated with the clothing designation icon 65, which indicates the clothing the user has decided to discard, checked (S122). The user may also directly check the checkbox 95 on the disposal suggestion screen. 【0230】 After the user confirms that the checkbox 95 for the clothing item they have decided to discard is checked, they select the "OK" icon 96. 【0231】 Based on the user terminal 20's acceptance of the selection of the "OK" icon 96 (S123), it sends an HTTP request containing the user ID and a disposal registration request to the management server 30 via the first communication interface 23 and the internet 11 (S124). The disposal registration request includes a clothing ID indicating the clothing that the user has decided to dispose of. 【0232】 The management server 30 receives an HTTP request containing the user ID and a disposal registration request through the second communication interface 33 (S124). The management server 30 identifies a record in the clothing management database that has a user ID and clothing ID that match the received user ID and clothing ID, and registers a disposal confirmation flag of "1" for the identified record (S125). The management server 30 also updates the user management database (S126). For example, if a disposal confirmation flag of "1" is registered for a record representing spring clothing, the number of spring clothing items and the total number of clothing items in the user management database are updated. 【0233】 The user inputs a termination command to the user terminal 20 by, for example, selecting "×" shown on the display screen of application 27 (S56). Based on the input of the termination command (S56), the user terminal 20 terminates the process (end). 【0234】 [Effects of the Embodiment] The cost per wear is calculated by dividing the purchase price of the clothing by the number of times it is worn, so it decreases each time the clothing is used. In other words, the cost per wear is an indicator of whether or not the clothing has been worn a number of times commensurate with the purchase price. When the cost per wear is determined to be below the target cost per wear (threshold cost), the user is notified to discard the clothing. In other words, the timing of the notification to discard the clothing is determined by considering the purchase price and the number of times the clothing has been worn. The user is satisfied that the clothing notified to discard has been worn a sufficient number of times commensurate with the purchase price, and discards the notified clothing. Therefore, the clothing management system 10 can notify the user to discard the clothing at the optimal timing, taking into account the purchase price and the number of times the clothing has been worn. 【0235】 The weight difference, calculated by subtracting the weight at the time of purchase from the current weight, is an indicator of changes in body shape between the time of purchase and the present. If the weight difference exceeds a threshold weight and the garment is deemed difficult to wear, the user will be notified to discard it. Therefore, the clothing management system 10 can notify the user to discard the garment at the optimal time, taking into account changes in the user's body shape. 【0236】 Even if the cost per wear is below the threshold price and the garment has been worn a sufficient number of times relative to the purchase price, if the garment has been properly cared for, the user is less likely to agree to its disposal, and it is appropriate to exclude it from the disposal notification. Whether or not a garment has been properly cared for is determined by whether or not its care point index is below the threshold index. Therefore, the timing of notifying users of disposal can be determined more appropriately than when it is determined solely by the cost per wear. 【0237】 Even if the cost per wear is below a threshold and the garment has been worn a sufficient number of times relative to its purchase price, it is reasonable to exclude garments that the user likes from the list of items to be discarded. Whether or not a garment is liked by the user is indicated by its ranking based on the frequency of wear. Garments with a high ranking are excluded from the list of items to be discarded. Therefore, the timing of notifying users of discarded items can be determined more appropriately than when the cost per wear is used alone. 【0238】 Whether a user likes their clothing is determined not only by how often they wear the clothing, but also by a care points index indicating the frequency of care the user has taken for the clothing, and by changes in the user's subjective rating of their preference. Therefore, the timing of notifying the user of the need to discard an item can be determined more appropriately than if it were determined solely by the frequency of wear. 【0239】 Because the target cost per wear (threshold cost) is adjusted using a weighting coefficient that varies depending on the type of clothing, the timing for notifying users of disposal can be determined more appropriately. 【0240】 For spring, summer, autumn, and winter clothing, a decision on whether or not to discard the items is made on the first and second decision dates before and after the estimated usage period for each season, and the user is notified accordingly. Therefore, the timing of notifying the user of the need to discard items can be determined more appropriately. 【0241】 [Differentiation] In the embodiment, an example was described in which the managed object of the clothing management system 10 is "clothing". In this modified example, an example is described in which the managed object of the clothing management system 10 is "shoes". Note that configurations other than those described below are the same as those described in the embodiment. Configurations identical to those in the embodiment are denoted by the same reference numerals as in the embodiment and their description is omitted. 【0242】 The server memory 32 of the management server 30 stores the user management database and shoe management database shown in Figure 14, instead of the user management database and clothing management database shown in Figure 2. Furthermore, the server memory 32 of the management server 30 stores the care scoring table and weighting table shown in Figures 3(D) and (E), instead of the care scoring table and weighting table shown in Figures 3(A) and (B). 【0243】 As shown in Figure 14(A), the user management database in this modified example includes multiple columns with the same names as the management database in the embodiment (see Figure 2(A)). However, the user management database in this modified example does not include a column named "Latest Weight". Since the user's foot size is not significantly affected by changes in weight, managing the user's current weight (latest weight) is unnecessary when the managed object is "shoes". 【0244】 The shoe management database shown in Figure 14(B) is a database that individually identifies the shoes owned by a user and manages data (information) related to those shoes. The data registered in the shoe management database is an example of management information. Note that the management information may include information other than that shown in Figure 14(B). 【0245】 The shoe management database has multiple columns, each labeled with the following names: "User ID", "Shoe ID", "Purchase Date", "Price", "Category 1", "Category 2", "Specified Favorite Rating", "Elapsed Time m", "Number of Uses B", "Unit Price", "Care Points", "Favorite Rating Score", "Favorite Rating Rank", "Photo Data", "Decision Date", "Decision Confirmed Flag", and "Disposal Confirmation Flag". 【0246】 The following columns, each labeled with the names "User ID," "Purchase Date," "Amount," "Category 2," "Specified Favorite Rating," "Elapsed Time m," "Care Points," "Favorite Rating Score," "Favorite Rating Rank," "Photo Data," "Decision Date," "Decision Confirmed Flag," and "Disposal Confirmation Flag," will contain data similar to that of the embodiment. 【0247】 Each field in the column named "Shoe ID" will contain a Shoe ID, which is an identifier that identifies each pair of shoes. The Shoe ID is an example of the identification information that is managed. 【0248】 Each field in the column named "Classification 1" will contain a shoe type, such as "Sandals," "Brand," or "Everyday Shoes." Classification 1 may also include other shoe types besides "Sandals," "Brand," and "Everyday Shoes," such as "Leather Shoes," "Sneakers," "Heels," "Boots," or "Pumps." 【0249】 Each field in the column named "Usage Count B" registers the number of times the user has worn the shoes from the date of purchase to the present. Based on when the user has worn the shoes, the user enters usage information indicating that the shoes have been worn into the user terminal 20 using the application 27. The management program 35 increments Usage Count B (by "1") based on receiving the usage information sent by the user terminal 20. Usage Count is an example of usage information. 【0250】 Each field in the column named "Usage Unit Price" registers the purchase price of the shoes and the usage unit price calculated from the number of times the shoes have been used B. The management program 35 calculates the usage unit price by dividing the purchase price of the shoes by the number of times the shoes have been used B, for example, based on an update to the number of times the shoes have been used, or just before deciding to discard the shoes, and registers it in the shoe management database. 【0251】 As shown in Figure 3(D), the maintenance scoring table has a column labeled "Maintenance Name" and a column labeled "Score". 【0252】 Each field in the column named "Maintenance Item Name" will contain entries for "Disinfectant / Deodorizing / Odor Removal Spray," "Brushing Dust Removal," "Cleaner Stain Removal," "Cream Application," "Hand Washing," "Professional Cleaning," and "Repair." In other words, the maintenance scoring table is a table that associates each maintenance item name with a corresponding score. 【0253】 As shown in Figure 3(E), the weighting table has a column named "Classification 1" and a column named "Weight Coefficient". 【0254】 Each field in the column labeled "Classification 1" contains information about shoe types, such as "Brand," "Everyday Shoes," and "Sandals." In other words, the weighting table is a table that associates shoe types with weight coefficients. 【0255】 The user terminal 20 and the management server 30 execute the processes shown in Figures 6 and 7. However, they skip the processes related to changes in body shape. Specifically, the user terminal 20 and the management server 30 skip steps S94 and S99 through S104. 【0256】 [Effects of the modification] The cost per use is calculated by dividing the purchase price of the shoes by the number of times they are used, so it decreases each time the shoes are used. In other words, the cost per use is an indicator of whether the shoes have been used a number of times commensurate with the purchase price. If the cost per use is determined to be below the target cost per use, the user is notified of the need to discard the shoes. That is, the timing of shoe disposal is notified to the user, taking into account the purchase price and the number of times the shoes have been used. The user accepts that the shoes notified of disposal have been used a sufficient number of times commensurate with the purchase price, and then discards the shoes in question. Therefore, the clothing management system 10 can notify the user of the need to discard the shoes at an appropriate time, taking into account the purchase price and the number of times the shoes have been used. 【0257】 Even if the unit price per use is below the threshold unit price and the shoes have been used a sufficient number of times relative to the purchase price, if the shoes are well-maintained, the user is less likely to agree to their disposal, and it is appropriate to exclude them from the disposal notification. Whether or not a pair of shoes is not well-maintained is determined by whether or not the maintenance point index is below the threshold index. Therefore, the timing of notifying users of disposal can be determined more appropriately than if it were determined solely by the unit price per use. 【0258】 Even if the cost per use is below a threshold and the shoes have been used a sufficient number of times relative to the purchase price, it is reasonable to exclude shoes that the user likes from the list of shoes to be discarded. Whether or not a shoe is liked by the user is indicated by a ranking determined by the frequency of use. Shoes with a high ranking are excluded from the list of shoes to be discarded. Therefore, the timing of notifying users of discarded shoes can be determined more appropriately than when the cost per use is used alone. 【0259】 Whether a user likes their shoes is determined not only by how often they wear them, but also by a care points index indicating how often they care for their shoes, and the user's designated favorite rating at the time of purchase and the most recent date. Therefore, the timing of notifying the user of disposal can be determined more appropriately than if it were determined solely by the frequency of use. 【0260】 Because the unit cost is adjusted using a weighting coefficient that corresponds to the type of shoe, it becomes possible to determine the timing of notifying users of disposal more appropriately. 【0261】 For spring, summer, autumn, and winter shoes, a decision on whether or not to discard them is made on the first and second decision dates before and after the estimated usage period for spring, summer, autumn, and winter, and the user is notified accordingly. Therefore, the timing of notifying the user of the need to discard the shoes can be determined more appropriately. 【0262】 [Other variations] In the embodiment, an example was described in which the disposal of clothing is determined based on changes in the user's body shape (step S99), cost per wear (step S107), care point index (steps S109, S111), and favorite ranking (step S110). However, the disposal of clothing may be determined solely by changes in the user's body shape (step S99), solely by cost per wear (step S107), solely by cost per wear (step S107) and care point index (steps S109, S111), solely by cost per wear (step S107) and favorite ranking (step S110), or solely by cost per wear (step S107), care point index (steps S109, S111), and favorite ranking (step S110). 【0263】 In one embodiment, an example was described in which the care points index is calculated by dividing the care points for care from the time of purchase to the present by the number of times the garment has been worn, B, from the time of purchase to the present. In other words, an example was described in which the frequency of care during the period from the time of purchase to the present is calculated as the care points index. However, the care points index may also be calculated by dividing the care points for care during a predetermined period, such as from the present to one year ago, by the number of times the garment has been worn during that predetermined period. In this case, the care points index indicates the frequency of care for the garment in question during the most recent year. 【0264】 In the embodiment, an example was described in which the disposal of clothing is determined by a care point index calculated by dividing the care points by the number of times worn B. However, the disposal of clothing may be determined by the care points themselves, rather than by the care point index. In other words, the decision to discard clothing may be based on the total amount of care performed, rather than the frequency of care. 【0265】 In the embodiment, an example was described in which the disposal of clothing is determined based on the favorite ranking, which is determined by the favorite ranking score (step S110). However, the decision to discard clothing may be made based on the favorite ranking score rather than the favorite ranking score. For example, in step S110, the user terminal 20 may decide to discard clothing based on whether the favorite ranking score is less than a threshold score pre-stored in the terminal memory 22. 【0266】 In the embodiment, an example was described in which the favorite score is determined comprehensively by the frequency of wearing the clothing, the frequency of maintenance, and the user's subjective change in favorite score. However, the favorite score may also be determined by only one or two of the following: the frequency of wearing the clothing, the frequency of maintenance, and the user's subjective change in favorite score. 【0267】 In the embodiment, an example was described in which the threshold unit price is corrected using a weighting coefficient according to the type of clothing (step S106). However, the weighting coefficient may be used to correct the wear price compared to the threshold unit price, rather than the threshold unit price itself. Specifically, the wear price is multiplied by the weighting coefficient and corrected. 【0268】 In the embodiment, the decision to discard clothing was made twice a year, on a first decision date and a second decision date, and an example was described in which the first and second decision dates differed depending on the type of clothing. However, the decision to discard clothing may also be made for all types of clothing, for example, monthly, every two months, every three months, or every four months. 【0269】 In the embodiment, a clothing management system 10 for managing clothing stored by hanging on hangers was described. However, the clothing management system 10 may also be used to manage clothing that is folded and stored in a chest of drawers, clothing cases, etc., instead of, or together with, clothing stored by hanging on hangers. 【0270】 Each screen described in the embodiments is merely an example, and other screens may be displayed on the touch panel 24 as long as they can accept input of the information described in the embodiments or notify the user of the information described in the embodiments. 【0271】 In the embodiment, an example was described in which the favorite score is calculated from the frequency of wear calculated from the number of times worn and the elapsed time, the frequency of care calculated from the care points and the number of times worn, and the change in the user's subjective favorite score calculated from the initial designated favorite score and the latest designated favorite score. A coefficient for level adjustment may be multiplied by any one or two of the three elements: the frequency of wear, the frequency of care, and the change in the user's subjective favorite score. 【0272】 In the embodiment, an example was described in which the user inputs information indicating whether or not clothing has been worn, that is, information indicating the number of times it has been worn (number of uses), through the user terminal 20 (app 27) (see Figures 10(B) and 11(A)). However, instead of user input, a sensor capable of detecting whether clothing has been worn may be used. The sensor may consist of, for example, a load sensor that detects the load applied to a hanger hanging bar in a closet, a proximity wireless IC tag attached to the hanger, and an installation terminal that can communicate with the load sensor, the IC tag, and the user terminal 20. The hanger number is stored in the IC tag. The installation terminal transmits the load data detected by the load sensor and the hanger number read from the IC tag via proximity wireless communication to the user terminal 20. The user terminal 20 (app 27) transmits the received load data and hanger number to the management server 30 via the communication interface 23 and the internet 11. The management program 35 of the management server 30 identifies the clothing ID that indicates the clothing worn by the user, based on the received load data and hanger number, and the clothing management database. Specifically, when a user removes clothing and a hanger from the closet, the load detected by the load sensor changes, and the installation terminal can no longer read the hanger number of that hanger from the IC tag. Therefore, it is possible to identify the clothing (clothing ID) that the user removed from the closet from the load data and hanger number. If the user wears the clothing they removed from the closet and returns the hanger to the closet, the hanger number can be read from the IC tag of that hanger, but the load detected by the load sensor does not return to its original value. Therefore, it is possible to identify the clothing (clothing ID) that the user removed from the closet and wore immediately from the load data and hanger number. Note that the sensors capable of detecting the wearing of clothing are not limited to load sensors, IC tags, and installation terminals, but may also be cameras that image the inside of the closet. The image data generated by the camera is transmitted to the management server 30 via the user terminal 20 and the internet 11. The management server 30 (management program 35) identifies the clothing (clothing ID) worn by the user by performing image analysis. 【0273】 In the embodiment, an example was described in which the user inputs their weight through the user terminal 20 (application 27) (see Figure 8(A)). However, instead of user input, a weighing scale that can communicate with the user terminal 20 may be used. The weighing scale transmits the measured weight to the user terminal 20. The user terminal 20 (application 27) transmits the received user weight to the management server 30 via the communication interface 23 and the internet 11. Alternatively, if there is a health management database that manages user information including the user's weight, the user terminal 20 (application 27) may obtain the user's weight from the health management database and transmit it to the management server 30. 【0274】 [Note 1] A user terminal having an input interface, a first communication interface, a display, and a first controller, It comprises a management server having a second communication interface, server memory, and a second controller, The above-mentioned first controller is, A management information acquisition process that acquires management information including the purchase price of the managed item, which is clothing or shoes, and information on the use of the managed item, The process involves sending the management information to the management server via the first communication interface and the Internet, and then executing the management information transmission process. The above second controller is, A management information registration process that stores the received management information in the server memory in association with the managed object identification information, A first determination process determines whether the unit price calculated by dividing the above purchase amount by the number of uses indicated by the above usage information is less than the threshold unit price, In the first determination process described above, a first disposal notification transmission process is performed, which transmits disposal notification information for the specified managed object, which is the managed object for which it has been determined that the unit price of use is less than the threshold unit price, to the user terminal via the second communication interface and the Internet. The above-mentioned first controller is, A clothing management system that executes a display process to display a disposal proposal screen indicating the disposal of the specific management target on the display based on receiving the above-mentioned disposal notice information. 【0275】 [Appendix 2] The management target is clothing, The management information includes the purchase weight, which is the user's weight at the time of purchase of the management target, The first controller, executes a latest weight transmission process to transmit the latest weight input through the input interface to the management server through the first communication interface, The second controller, performs a second determination process to determine whether the weight difference calculated by subtracting the purchase weight from the latest weight is greater than or equal to a threshold weight, and a second disposal notice transmission process to transmit disposal notice information for the specific management target determined to have a weight difference greater than or equal to the threshold weight in the second determination process to the user terminal through the second communication interface and the Internet. The clothing management system according to Appendix 1. 【0276】 [Appendix 3] The management information includes maintenance information regarding maintenance performed on the management target, The second controller, performs a first calculation process to calculate a care point index obtained by quantifying the frequency of maintenance performed on the management target based on the maintenance information, and a third determination process to determine whether the care point index is less than a threshold index. The first disposal notice transmission process, The clothing management system described in Appendix 1, wherein, in the first judgment process described above, it is determined that the usage unit price is less than the threshold unit price, and in the third judgment process described above, it is determined that the care point index is less than the threshold index, and the disposal notification information for the specified managed item, which is the managed item, is transmitted to the user terminal via the second communication interface. 【0277】 [Note 4] The second controller described above performs a second calculation process that calculates a favorite score for each managed object, which indicates the user's level of liking based on the frequency of use indicated by the number of uses and the usage period described above. A fourth decision process is performed to rank the above-mentioned managed items based on the above-mentioned favorite score and to determine whether the rank is below a threshold rank. The above first disposal notification transmission process is: The clothing and other items management system described in Appendix 1, wherein, in the first judgment process described above, it is determined that the usage unit price is less than the threshold unit price, and in the fourth judgment process described above, it is determined that the rank is less than the threshold rank, and the disposal notification information for the specified managed item, which is the managed item, is transmitted to the user terminal via the second communication interface. 【0278】 [Note 5] The above management information includes maintenance information regarding maintenance performed on the above managed objects. The above second controller is, Based on the above maintenance information, a first calculation process is performed to calculate a maintenance point index that quantifies the frequency of maintenance performed on the above-mentioned managed object. The clothing management system described in Appendix 4 includes a process for correcting the above-mentioned favorite score by the above-mentioned care point index, or the said care point index and the specified favorite score entered by the user. 【0279】 [Note 6] The above management information includes category information indicating the type of managed object. The above category information and weight coefficients are associated with each other. The above second controller is, A clothing management system as described in Appendix 1, which performs a correction process to correct the above-mentioned usage unit price or the above-mentioned threshold unit price by the above-mentioned weight coefficient. 【0280】 [Note 7] The above management information includes category information indicating the type of managed object. The above category information is associated with the first decision date before the estimated usage period of the above-mentioned managed object and the second decision date after the estimated usage period. The above first decision process is, The clothing and other items management system described in Appendix 1, which is implemented on the above-mentioned first and second decision dates for the applicable types of managed items. 【0281】 [Note 8] A user terminal having an input interface, a first communication interface, a display, and a first controller, It comprises a management server having a second communication interface, server memory, and a second controller, The above-mentioned first controller is, A management information acquisition process that acquires management information including the user's weight at the time of purchase, which is the user's weight at the time of purchase of the managed item, which is clothing or shoes. A management information transmission process that transmits the management information to the management server via the first communication interface and the Internet, The process of transmitting the latest weight entered through the above input interface to the management server via the above first communication interface is performed. The above second controller is, A management information registration process that stores the received management information in the server memory in association with the managed identification information, and stores the latest weight in the server memory, A judgment process to determine whether the weight difference calculated by subtracting the weight at the time of purchase from the latest weight is greater than or equal to a threshold weight, Execute a waste notification sending process that sends waste notification information for a specific management object, which is the management object determined to have a weight difference greater than or equal to the threshold weight in the above determination process, to the user terminal. The first controller An apparel management system that executes a display process for causing the display to display a waste proposal screen indicating the disposal of the specific management object based on receiving the waste notification information. 【0282】 [Appendix 9] A program implemented on a user terminal equipped with an input interface, a communication interface, a display, and a computer, A management information reception process for receiving, through the input interface, input of management information including type information indicating the type of the management object, which is purchased clothing or shoes, and the purchase amount, A management information transmission process for transmitting the management information to a management server through the communication interface and the Internet, A usage information reception process for receiving, through the input interface, input of usage information indicating the number of times of use of the management object, A usage information transmission process for transmitting the usage information to the management server through the communication interface, A program for causing the computer to execute a display process for receiving waste notification information transmitted by the management server and displaying, on the display, a specific management object that is the management object indicated by the waste notification information. 【0283】 [Appendix 10] A program implemented on a user terminal equipped with an input interface, a communication interface, a display, and a computer, A management information reception process for receiving, through the input interface, input of management information including type information indicating the type of purchased clothing and the weight at the time of purchase, A management information transmission process for transmitting the management information to a management server through the communication interface and the Internet, The latest weight input process accepts the latest weight through the input interface described above, The latest weight transmission process involves sending the latest weight to the management server via the communication interface mentioned above. A program that receives disposal notification information sent by the management server and causes the computer to perform a display process that displays the specific garment indicated by the disposal notification information on the display. [Explanation of symbols] 【0284】 10. Clothing and other items management system 11. Internet 20. User terminals 21. CPU (an example of a computer) 22. Terminal Memory 23. Communication Interface (An example of the first communication interface) 24... Touch panel 25...Camera 30. Management Server 31..CPU 32... Server memory 33. Communication Interface (An example of a second communication interface) 35. Management Program

Claims

[Claim 1] A user terminal having an input interface, a first communication interface, a display, and a first controller, It comprises a management server having a second communication interface, server memory, and a second controller, The first controller described above is A management information acquisition process that acquires management information including the purchase price of the managed item, which is clothing or shoes, and information on the use of the managed item, The process involves transmitting the management information to the management server via the first communication interface and the Internet, and then executing the management information transmission process. The second controller described above is: A management information registration process that stores the received management information in the server memory in association with the managed object identification information, A first determination process determines whether the unit price calculated by dividing the above purchase amount by the number of uses indicated by the above usage information is less than the threshold unit price, In the first determination process described above, a first disposal notification transmission process is performed, which transmits disposal notification information for the specified managed object, which is the managed object for which it has been determined that the unit price of use is less than the threshold unit price, to the user terminal via the second communication interface and the Internet. The first controller described above is A clothing and other items management system that, upon receiving the above-mentioned disposal notification information, executes a display process to show a disposal suggestion screen indicating the disposal of the above-mentioned specified items on the display. [Claim 2] The items subject to the above management are clothing. The above management information includes the user's weight at the time of purchase of the managed item, The first controller described above is The latest weight transmission process is executed, which transmits the latest weight entered through the above input interface to the management server through the above first communication interface. The second controller described above is: A second judgment process determines whether the weight difference calculated by subtracting the weight at the time of purchase from the most recent weight is greater than or equal to a threshold weight, The clothing and other items management system according to claim 1, further comprising: a second disposal notification transmission process that transmits disposal notification information for the specified managed items for which the weight difference is determined to be greater than or equal to the threshold weight in the second judgment process described above, to the user terminal via the second communication interface and the Internet. [Claim 3] The above management information includes maintenance information regarding maintenance performed on the above managed objects. The second controller described above is: Based on the above maintenance information, a first calculation process calculates a maintenance point index that quantifies the frequency of maintenance performed on the above-mentioned managed object, A third judgment process is performed to determine whether the above care point index is less than the threshold index, The above first disposal notification transmission process is: The clothing management system according to claim 1, wherein in the first determination process, it is determined that the usage unit price is less than the threshold unit price, and in the third determination process, it is determined that the care point index is less than the threshold index, and the disposal notification information for the specified managed item, which is the managed item, is transmitted to the user terminal via the second communication interface. [Claim 4] The second controller described above includes a second calculation process that calculates a favorite score for each managed object, which indicates the user's level of liking based on the frequency of use indicated by the number of uses and the usage period, A fourth decision process is performed to rank the above-mentioned managed items based on the above-mentioned favorite score and to determine whether the rank is below a threshold rank. The above first disposal notification transmission process is: The clothing management system according to claim 1, wherein in the first determination process, it is determined that the usage unit price is less than the threshold unit price, and in the fourth determination process, it is determined that the rank is less than the threshold rank, and the disposal notification information for the specified managed object, which is the managed object, is transmitted to the user terminal via the second communication interface. [Claim 5] The above management information includes maintenance information regarding maintenance performed on the above managed objects. The second controller described above is: Based on the above maintenance information, a first calculation process is performed to calculate a maintenance point index, which is a numerical representation of the frequency of maintenance performed on the above-mentioned managed object. The clothing management system according to claim 4, wherein the second calculation process described above includes a process of correcting the favorite score based on the care point index, or the care point index and a specified favorite score entered by the user. [Claim 6] The above management information includes category information indicating the type of managed object. The above category information and weight coefficients are associated with each other. The second controller described above is: The clothing management system according to claim 1, which performs a correction process to correct the above-mentioned usage unit price or the above-mentioned threshold unit price by the above-mentioned weight coefficient. [Claim 7] The above management information includes category information indicating the type of managed object. The above category information is associated with the first decision date before the estimated usage period of the above-mentioned managed object and the second decision date after the estimated usage period. The above first decision process is, The clothing and other items management system according to claim 1, which is executed on the above-mentioned first decision date and second decision date for the above-mentioned items of the applicable type. [Claim 8] A management program implemented in a management server having a communication interface, server memory, and a controller, Management information registration process includes management information that includes the purchase price of the managed item, which is clothing or shoes, and usage information of the managed item, and which receives the management information transmitted by the user terminal and stores the received management information in the server memory in association with the managed item identification information. A determination process to determine whether the unit price calculated by dividing the above purchase amount by the number of uses indicated by the above usage information is less than the threshold unit price, A management program that causes the controller to execute a disposal notification transmission process, which transmits disposal notification information for the specified managed object, which is the managed object for which the above determination process determines that the above usage unit price is less than the above threshold unit price, to the user terminal via the above communication interface and the Internet.

Images