WO2018034000A1 - Information processing device, information processing method, program and storage medium - Google Patents

Information processing device, information processing method, program and storage medium Download PDF

Info

Publication number
WO2018034000A1
WO2018034000A1 PCT/JP2016/074231 JP2016074231W WO2018034000A1 WO 2018034000 A1 WO2018034000 A1 WO 2018034000A1 JP 2016074231 W JP2016074231 W JP 2016074231W WO 2018034000 A1 WO2018034000 A1 WO 2018034000A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
reporter
recipe
approval
posted
Prior art date
Application number
PCT/JP2016/074231
Other languages
French (fr)
Japanese (ja)
Inventor
有紀 内田
Original Assignee
楽天株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 楽天株式会社 filed Critical 楽天株式会社
Priority to PCT/JP2016/074231 priority Critical patent/WO2018034000A1/en
Priority to JP2017551734A priority patent/JP6254753B1/en
Publication of WO2018034000A1 publication Critical patent/WO2018034000A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services

Definitions

  • the present invention relates to an information processing apparatus and an information processing method, a program for realizing the information processing apparatus, and a storage medium storing the program, and in particular, a processing technique related to approval of a report for a recipe posted on a website. Related to the field.
  • Websites that accept recipe submissions for dishes and post posted recipes are widely known.
  • Each user can post a recipe by inputting information such as material information such as used ingredients and seasonings and the amount of each material on a predetermined input page prepared on the site side, for example.
  • the poster of the recipe is referred to as “Recipa”.
  • each user at the recipe site can browse the recipe presented through the site and create a dish according to the recipe. Furthermore, the user who created the dish according to the recipe can post an impression about the created dish, a comment on the recipe, and the like as a “report” on the site.
  • report contributors are referred to as “reporters”. Submitted reports are generally posted on the site after receiving approval from the receiver. Depending on the recipe site, an incentive such as a point may be given to the contributor depending on the posting of the report.
  • the approval of the posting report by the receiver is particularly burdensome for popular receivers (recipers with a large number of recipes viewed), recipes with a large number of recipe postings, and the approval may be delayed. Delaying approval is undesirable because it may lead to loss of communication opportunities between the receiver and the reporter.
  • the present invention has been made in view of the above-mentioned circumstances, and while reducing the burden on the reporter's report approval, the receiver and the reporter are able to simultaneously suppress the deterioration of the quality of the report publication page and the reduction in the number of report publications.
  • the purpose is to promote communication with each other.
  • the information processing apparatus provides the intimacy between a reporter who is a user who has posted a recipe on a website for posting a recipe and a reporter who is a user who has posted a report on a posted recipe by the receiver.
  • an intimacy evaluation unit that evaluates based on information associated with each reporter and an intimacy reporter that is a reporter with a certain degree of intimacy or more, submits the report, the reporter is requested to approve the report.
  • a certification control unit in which comprises a.
  • the posting report of the intimate reporter is automatically approved as time elapses, so that it is possible to save the trouble of approving the reporter for those reports.
  • by performing automatic approval it is possible to suppress a decrease in the number of reports published.
  • the report by the non-intimate reporter is not subject to automatic approval, and manual approval by the receiver is required. For this reason, the deterioration of the quality of the posted report is suppressed.
  • requesting manual approval of a receiver in a report by a non-intimate reporter gives the receiver an opportunity to communicate with the non-intimate reporter. It is possible.
  • the promotion of communication in this way contributes to the improvement of intimacy between the receiver and the intimate reporter, and the report can be automatically approved the next time a report is posted from the intimate reporter. Increases nature. Increasing the possibility of automatic approval contributes to reducing the burden associated with the reporter's report approval.
  • an inappropriate reporter determination unit that determines whether or not the reporter is an inappropriate reporter based on a result of evaluating information reliability of a report posted by the reporter in the past.
  • the approval control unit determines whether the report is an inappropriate report that is a report posted by the inappropriate reporter before requesting the receiver to approve the unapproved report. If it is determined that there is, it is possible not to request approval for the report.
  • the inappropriate reporter determination unit posts a report using the same or similar images to a plurality of recipes as to whether or not the reporter is the inappropriate reporter. It is possible to determine based on whether or not there is.
  • the closeness evaluation unit can evaluate the closeness based on the number of past report approvals to the reporter by the receiver.
  • the number of past report approvals for the reporter by the receiver functions as an index for estimating the frequency of communication between the two. Further, a reporter whose posting report has not been automatically approved is designed to automatically approve the posting report while repeating the posting of the report to the receiver. In other words, the reporter saves time and effort to approve the report for the same reporter while repeating report approval for the same reporter.
  • the closeness evaluation unit can evaluate the closeness based on the reporter's report posting count for the posting recipe by the reporter.
  • the number of reporter submissions for the recipe submitted by the reporter also serves as an index for estimating the frequency of communication between the two.
  • the closeness evaluation unit can evaluate the closeness based on the number of approvals for the posting report of the receiver for the posting recipe by the reporter.
  • the approval control unit can adjust the timing for requesting the approval based on the analysis result of the report approval behavior of the receiver in the past.
  • the approval control unit when there are a plurality of unapproved reports as posting reports for the recipe recipe of the receiver, the approval control unit is configured to request individual approval reports for the receiver. It is possible to make a request in a format in which an approval instruction operation can be performed.
  • the approval control unit can make a request in a format that allows the reporter to perform a registration instruction operation to the intimate reporter as an approval request for the receiver.
  • the approval control unit may be posted on the website on condition that the report is approved and a reply is input from the receiver. It is possible to control.
  • the approval control unit when there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, the approval control unit is configured as an individual unapproved report as a request for approval for the receiver. It is possible to make a request in a format in which the reply can be input.
  • the approval control unit can accept input of fixed reply information, which is information in which the reply content is set to a fixed content, as the reply input.
  • the information processing method according to the present invention provides a degree of intimacy between a reporter who is a user who has posted a recipe on a website posting a recipe and a reporter who is a user who has posted a report on a recipe posted by the receiver.
  • An intimacy evaluation step that evaluates based on information associated with each reporter, and an intimate reporter that is a reporter with an intimacy greater than a certain degree posts the report, the reporter approves the report
  • the report approval process is performed according to the passage of time without manual approval from the receiver, and when a non-intimate reporter who is a reporter whose intimacy is not the predetermined level or more submits a report, While requesting the reporter to approve the report, report approval processing over time And admission control step is not performed, which is a processing method of an information processing apparatus executes. Also by such an information processing method, an operation similar to that of the information processing apparatus according to the present invention described above can be obtained.
  • a program according to the present invention is a program that causes an information processing apparatus to execute processing executed as the information processing method.
  • a storage medium according to the present invention is a storage medium storing the program. The above information processing apparatus is realized by these programs and storage media.
  • the communication between the receiver and the reporter is promoted while at the same time suppressing the deterioration in the quality of the report publication page and the reduction in the number of report publications. be able to.
  • First Embodiment> [1-1. Overview of network system] [1-2. Hardware configuration of computer device] [1-3. Approval control method as the first embodiment] [1-4. Processing procedure] [1-5. Summary of First Embodiment] ⁇ 2. Second Embodiment> [2-1. Approval control method as the second embodiment] [2-2. Processing procedure] [2-3. Summary of Second Embodiment] ⁇ 3. Program and Storage Medium> ⁇ 4. Modification>
  • FIG. 1 shows an example of a network system 1 assumed in the present embodiment.
  • the recipe site server 31 and the plurality of user terminals 4 in the recipe site operating system 3 can communicate with each other via a network 2 as the Internet.
  • the user terminal 4 is a computer device provided with a web browser.
  • Examples of the user terminal 4 include a high-function mobile phone (smart phone), a mobile phone, a portable information terminal (tablet terminal), and a portable or stationary personal computer (PC). It is not limited to.
  • the user terminal 4 requests a web page or predetermined processing by transmitting an HTTP (Hypertext Transfer Protocol) request to the recipe site server 31 or the like in the recipe site operating system 3.
  • the user terminal 4 receives web page data (for example, HTML (HyperText Markup Language) data) sent in response to the HTTP request, and performs a web page display process by the web browser based on the web page data. . Thereby, the user can browse and operate a desired web page.
  • HTTP Hypertext Transfer Protocol
  • HTML HyperText Markup Language
  • the recipe site management system 3 includes a recipe site server 3a, a user DB (database) 32, a recipe DB 33, a report DB 34, and an intimacy information DB 35, each of which is constituted by a computer device. Each of these devices can communicate with each other via a network such as a LAN (Local Area Network).
  • a network such as a LAN (Local Area Network).
  • the recipe site server 31 is an information processing apparatus that performs various processes related to a recipe site, which is a website where a recipe for posting a recipe for cooking and a recipe are presented.
  • the user DB 32 stores various types of information related to users who use the recipe site.
  • the user can register as a member in the recipe site management system 3 when using the recipe site.
  • the user registers necessary information such as contact information such as a user ID (user identification information), a password, a name, and an e-mail address.
  • the user can receive various services required for login provided by the recipe site by logging in to the recipe site using the registered user ID and password. For example, posting a recipe described below, posting a creation report for a recipe, and the like.
  • the user DB 32 various types of information related to users as members are stored for each user ID.
  • the user DB 32 stores the necessary information as information related to the user. Further, the user DB 32 also stores information (hereinafter referred to as “behavior history information”) related to various behavior histories of the user at the recipe site, such as recipe browsing and favorite recipe registration.
  • behavior history information information related to various behavior histories of the user at the recipe site, such as recipe browsing and favorite recipe registration. The action history information in this example will be described later.
  • the recipe site server 31 performs various processes based on the HTTP request sent from the user terminal 4. For example, a web page for accepting submission of a recipe is presented to the user, and recipe information (information indicating the contents of the recipe) is registered in the recipe DB 33 based on information input to the web page.
  • the recipe information includes, for example, information on a recipe name, a cooking ID, a genre, the number of people, used ingredients and their amounts, used seasonings and their amounts, cooking procedures, and cooking images.
  • the dish ID is an identifier for identifying a dish created according to the recipe information.
  • the genre information is genre information to which the dish belongs, and includes various classifications such as “meat dish”, “fish dish”, “salad”, and “drink”, for example.
  • the information on the number of persons is information indicating how many servings the target dish created according to the recipe information.
  • the dish image is an image that should represent the finished dish, and for example, a posted image by the user is used.
  • the posted recipe is assigned a recipe ID, which is an identifier for uniquely identifying the recipe, and the recipe information is associated with (associated with) the recipe ID and stored in the recipe DB 33. .
  • the recipe site server 31 performs processing for posting a recipe on the recipe site based on the storage information of the recipe DB 33. Specifically, the recipe site server 31 of this example performs a recipe search process based on a search condition such as a search keyword specified by the user, and presents a web page on which a recipe that matches the search condition is presented to the user I do.
  • a search condition such as a search keyword specified by the user
  • the recipe site server 31 accepts submission of a creation report from the user who created the dish according to the recipe information.
  • the creation report is information that can be posted for each recipe.
  • the creation report is information that should include information such as an impression of creating a dish and a comment on a recipe.
  • as a creation report not only text information but also an image representing the created dish can be posted.
  • the recipe site server 31 presents the user with a web page for accepting submission of a creation report, and performs processing for registering the creation report in the report DB 34 based on information input to the web page.
  • a report ID which is an identifier for uniquely identifying the created report, is assigned to the posted created report.
  • the recipe site server 31 stores information on the created report and the user ID of the poster in the report DB 34 in association with the report ID.
  • reporter the user who posted the creation report.
  • the recipe site server 31 receives an input of a reply comment from the receiver for the created creation report. Furthermore, the recipe site server 31 receives an input of a comment from a reporter for a reply comment. When there is an input of a reply comment or reply comment from the reporter by the reporter, the recipe site server 31 corresponds the input reply comment or comment information for the reply comment with the report ID of the corresponding creation report. Then, it is stored in the report DB 34.
  • FIG. 2 is a diagram showing an example of the creation report.
  • a creation report posted for a recipe is posted on the recipe posting page.
  • a recipe posting page is referred to as a “recipe page”.
  • recipe information corresponding to a recipe designated by the user through the above-described recipe search process or the like is posted.
  • the recipe page in this case includes recipe name information area Ar1 in which recipe name information is posted, dish photo posting area Ar2 in which dish photos are posted, and ingredients used, as recipe information information areas.
  • a material / quantity posting area Ar3 in which used ingredients, used seasonings and information on their quantities are respectively posted
  • a cooking procedure posting area Ar4 in which information on cooking procedures is posted.
  • the recipe page in this case is provided with a report posting area Ar5 in which a creation report posted for the posted recipe on the recipe page is posted.
  • a plurality of created reports can be posted.
  • the posting area of each created report there is an area for posting posted photo images and text, and when there is a reply comment from a receiver and a comment input from a reporter for the reply comment Is provided with a button (“view other comments” in the figure) for instructing presentation of the comment information.
  • the created creation report is posted on the recipe page under the condition that it is approved by the receiver in this embodiment.
  • the recipe page of this example can also be called a report posting page in the sense that a creation report is posted.
  • the action history information regarding these various actions is stored in the user DB 32 based on the result of the recipe site server 31 monitoring the user's actions.
  • the recipe site server 31 stores the recipe ID of the recipe viewed by the user in association with the user ID of the user.
  • recipe posting history information the recipe ID of the recipe posted by the user is stored in association with the user ID of the user
  • report posting history information the report ID of the created report posted by the user, and the created report
  • the recipe ID of the posting destination recipe is stored in association with the user ID of the user.
  • approval history information the report ID of the created report approved by the user and the user ID of the reporter who posted the created report are stored in association with the user ID of the user, and the reply history to the report is stored.
  • the report ID of the created report for which the user has input a reply comment is stored in association with the user ID of the user.
  • each action history information stored in the user DB 32 such as the above recipe browsing history information, recipe posting history information, report posting history information, approval history information, reply history information, etc. Is also stored.
  • the inappropriate flag Fi and the delay tendency flag Fd are stored in association with each user ID.
  • the inappropriate flag Fi and the delay tendency flag Fd will be described later.
  • FIG. 1 various examples of the configuration of the network 2 are assumed.
  • the Internet intranet, extranet, LAN (Local Area Network), CATV (Community Antenna TeleVision) communication network, virtual private network, telephone line network, mobile communication network, satellite communication network, etc.
  • Various examples of transmission media constituting all or part of the network 2 are also envisaged.
  • IEEE Institute of Electrical and Electronics Engineers 1394, USB (Universal Serial Bus), power line carrier, telephone line etc. wired, infrared such as IrDA (Infrared Data Association), Bluetooth (registered trademark), 802.11 wireless It can also be used by radio such as a mobile phone network, satellite line, and digital terrestrial network.
  • FIG. 3 shows a hardware configuration of a computer device constituting each device (user DB 32, recipe DB 33, report DB 34, intimacy information DB 35, and user terminal 4) including the recipe site server 31 shown in FIG.
  • a CPU (Central Processing Unit) 101 of a computer apparatus performs various processes according to a program stored in a ROM (Read Only Memory) 102 or a program loaded from a storage unit 108 to a RAM (Random Access Memory) 103. Execute the process.
  • the RAM 103 also appropriately stores data necessary for the CPU 101 to execute various processes.
  • the CPU 101, ROM 102, and RAM 103 are connected to each other via a bus 104.
  • the input / output interface 105 is also connected to the bus 104.
  • the input / output interface 105 includes an input unit 106 including a keyboard, a mouse, and a touch panel, a display (display device) including an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), an organic EL (Electroluminescence) panel, and a speaker.
  • a storage unit 108 composed of an HDD (Hard Disk Drive) or a flash memory device, and a communication unit 109 for mutual communication with an external device.
  • a media drive 110 is also connected to the input / output interface 105 as necessary, and a removable medium 111 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and information can be written to the removable medium 111. Reading is performed.
  • a removable medium 111 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and information can be written to the removable medium 111. Reading is performed.
  • data and programs can be uploaded and downloaded through communication by the communication unit 109, and data and programs can be transferred via the removable medium 111.
  • the CPU 101 performs processing operations based on various programs, information processing and communication described below are executed particularly in the computer device as the recipe site server 31.
  • the recipe site server 31 is not limited to a single computer device as shown in FIG. 3, and a plurality of computer devices may be configured as a system. Good.
  • the plurality of computer devices may be systemized by a LAN or the like, or may be arranged at a remote place by a VPN using the Internet or the like.
  • the recipe site server 31 can be expressed as having a closeness evaluation processing unit F1, an inappropriate reporter determination processing unit F2, and an approval control processing unit F3 for each function.
  • the familiarity evaluation processing unit F1 evaluates the familiarity between the receiver and the reporter based on information associated with the receiver and the reporter.
  • the familiarity evaluation processing unit F1 in this example evaluates the familiarity between the receiver and the reporter based on the action history information stored in the user DB 32. Specifically, the familiarity evaluation processing unit F1 evaluates the familiarity between the two based on the past report approval count for the reporter by the receiver. For example, if user A is a reporter, and user B is a reporter who has posted a creation report for user A's posted recipe, user B can create a report that has been posted by user A in the past. The number of approved created reports is specified as the above “number of report approvals”.
  • the number of past report approvals for the reporter by the receiver functions as an index for estimating the communication frequency between the two. For this reason, it is possible to appropriately evaluate the intimacy between the receiver and the reporter by specifying the number of report approvals.
  • a reporter as an “intimate reporter” whose intimacy with a receiver is a certain degree or higher, a report posted to the receiver is automatically approved. . For this reason, being able to appropriately evaluate the intimacy as described above means that a reporter with a relatively high degree of intimacy can be automatically approved.
  • the closeness evaluation processing unit F1 determines the familiarity based on the number of report submissions of the reporter to the posted recipe by the reporter. evaluate. At this time, the intimacy evaluation processing unit F1 also considers the number of approvals for the reporter posting report for the posting recipe by the reporter. Specifically, the intimacy evaluation processing unit F1 of this example specifies the above-mentioned “report approval count” and reports the reporter when the reporter has posted a created report in the past with respect to the posting recipe by the reporter. The number of postings of the reporter for the posting recipe by and the number of times the reporter has approved the posting report of the receiver. Then, the closeness between the receiver and the reporter is calculated based on the specified number of times. In this example, the total value of these specified number of times is calculated as the familiarity.
  • the reporter's report submission count for the posting recipe by the reporter also functions as an index for estimating the communication frequency between the two. Therefore, by evaluating the intimacy as described above, it is possible to appropriately evaluate the intimacy between both the receiver and the reporter. Furthermore, it is possible to automatically approve reporters with relatively high intimacy.
  • the intimacy between the receiver and the reporter is more appropriately evaluated, and the intimacy accuracy is even higher. Reporter can be automatically approved.
  • the inappropriate reporter determination processing unit F2 determines whether or not the reporter is an inappropriate reporter based on the result of evaluating the information reliability of the report posted by the reporter in the past.
  • the recipe site may give incentives such as points to the reporter every time a creation report for a recipe is posted. In that case, the information reliability is low for the purpose of earning incentives, etc.
  • Reporters that post a relatively large amount of created reports may appear. For this type of reporter, requesting approval from the receiver for the post report is undesirable because it increases the burden on the approval of the receiver. For this reason, in this embodiment, this type of reporter is specified as an “unsuitable reporter”, and a post report from the unsuitable reporter is excluded from the approval request as described later.
  • the inappropriate reporter determination processing unit F2 of this example determines whether or not the reporter is an inappropriate reporter based on whether or not the reporter has posted reports using the same or similar images to a plurality of recipes. For unsuitable reporters for the purpose of rough earning such as points, it is troublesome to take pictures of the dishes created when posting the creation report, such as changing the same image or the overall brightness and color slightly It has been confirmed that similar images, such as those with relatively minor image processing, are reused between submission reports for each of a plurality of recipes.
  • the inappropriate reporter determination processing unit F2 first identifies a plurality of generated reports with different posting destination recipes from among the generated reports posted by the target reporter in the past, and is used in those generated reports. Get each image you have. Then, for each acquired image, the degree of similarity between all the other acquired images is calculated, and images having a degree of similarity greater than or equal to a certain value are specified as the same or similar images. At this time, for example, it is conceivable that the target reporter uses the same or similar images for each dish. In this case, a plurality of sets can be specified as the same or similar images.
  • a known method can be adopted as a method for evaluating the similarity between images.
  • the degree of coincidence of the edges detected from each image to be compared can be calculated as the similarity.
  • an average pixel value difference is calculated between target images for each area constituting the image, such as an area with a 4 ⁇ 4 pixel size, and the total value of the differences is calculated as a similarity.
  • a technique can also be adopted, and the technique for evaluating the degree of similarity is not limited to a specific technique.
  • the inappropriate reporter determination processing unit F2 determines that the target reporter is an inappropriate reporter if the number of identified identical or similar images is equal to or greater than a certain value. This corresponds to determining that the reporter is an inappropriate reporter if the information reliability of the posted report by the target reporter is below a certain level.
  • a plurality of sets of the same or similar images are specified as described above, that is, when a plurality of the same or similar images are calculated, if the maximum number among them is a certain value or more, , It is determined that the target reporter is an inappropriate reporter.
  • the same or similar images are referred to as “same / similar images”.
  • the inappropriate reporter determination processing unit F2 sets the inappropriate flag Fa associated with the reporter's user ID and stored in the user DB 32 from OFF (for example, “0”) to ON (for example, “1”). )) Is performed.
  • the approval control processing unit F3 performs control related to the approval of the created report posted by the reporter based on the closeness between the reporter and the reporter evaluated by the closeness evaluation processing unit F1. Specifically, the approval control processing unit F3, when an intimate reporter that is a reporter with a closeness of a certain degree or more, submits a report, after requesting the reporter to approve the report, manual approval from the receiver Even if not, the report approval process is performed according to the passage of time, and if a non-intimate reporter who is a reporter whose intimacy is not more than a certain degree posts the report, the reporter is requested to approve the report, but the time has passed The report approval process according to is not performed.
  • the approval request is performed for both the posting report by the intimate reporter and the posting report by the non-intimate reporter, but the report approval processing according to the passage of time, that is, the automatic approval by the recipe site server 31 is performed. It is performed only for the contribution report by.
  • the intimacy reporter determination performed by the approval control processing unit F3 will be described.
  • the familiarity evaluation processing unit F1 calculates the familiarity between the receiver and the reporter, and the approval control processing unit F3 is based on the calculated familiarity. Determine whether the reporter is an intimate reporter.
  • the approval control processing unit F3 of the present example uses different intimacy calculation methods depending on whether or not the reciever evaluation processing unit F1 has posted a creation report in the past for a posting recipe by a reporter. Corresponding to the selection, it is determined whether the reporter is an intimate reporter using different threshold values.
  • the intimacy is set to a threshold value (hereinafter referred to as “first” It is determined whether or not it is an intimate reporter by whether or not it is greater than or equal to the “intimacy threshold”, and the intimacy calculated when the reporter has posted a creation report in the past for the posting recipe by the reporter, Whether or not the intimacy is an intimacy reporter is determined based on whether or not the intimacy is equal to or higher than a threshold (hereinafter referred to as “second intimacy threshold”) set in correspondence with the case.
  • the approval control processing unit F3 stores information indicating that the reporter is an intimate reporter in the intimacy information DB 35. Specifically, the user ID of the reporter determined to be an intimate reporter is stored in association with the user ID of the reporter.
  • FIG. 5 is a diagram illustrating information stored in the intimacy information DB 35.
  • the intimacy information DB 35 By performing the storage process by the approval control processing unit F3 as described above, in the intimacy information DB 35, information indicating which user is the intimacy reporter for the user is constructed for each user as a receiver.
  • the approval control processing unit F3 controls the approval of the created report based on the determination result of the intimate reporter as described above. Specifically, when an intimate reporter for a receiver submits a creation report to a recipe submitted by a certain receiver, the approval control processing unit F3 requests the receiver to approve the creation report, and then creates the creation from the receiver. Even if the report is not manually approved, the report approval process is performed according to the passage of time. In addition, when a non-intimate reporter who is not an intimate reporter for a recipe for a recipe submitted by a certain receiver submits a creation report, the request for approval of the creation report is requested from the receiver, while the time elapsed for the creation report. The report approval process according to is not performed.
  • the approval request for the created report will be described.
  • the approval request is made by sending an e-mail to the target receiver.
  • an e-mail requesting approval in this way is referred to as an “approval request mail”.
  • the approval request for the created report is made in a format that requests approval for the multiple unapproved reports at once.
  • FIG. 6 shows an example of an approval request mail in a format that requests approval for a plurality of unapproved reports in this way.
  • a message requesting approval for the unapproved report is presented, and information for specifying the unapproved report requesting approval, specifically the unapproved report in the example of FIG. Image and text information representing the content of the post will be presented.
  • an approval check box Cb1 is provided for each unapproved report for enabling an approval instruction operation for each unapproved report.
  • the user checks the approval check box cb1 provided for the corresponding unapproved report, and operates the send button B1 provided in the approval request mail.
  • information instructing approval for the checked unapproved report is returned to the recipe site server 31, and the recipe site server 31 (approval control processing unit F ⁇ b> 3) determines the corresponding unapproved report based on the information. Perform the approval process.
  • a request for approval to the receiver a request is made in a format that allows an approval instruction operation for each unapproved report.
  • the ease of report approval by the receiver increases, and the effect of suppressing the reduction in the number of report publications can be enhanced.
  • communication between the receiver and the non-intimate reporter can be promoted.
  • the approval request mail in this case is provided with a registration check box cb2 for enabling a registration instruction operation to the intimate reporter of the reporter who posted the unapproved report.
  • the registration check box cb2 is provided in the approval request mail only when the posting reporter of the created report that requires approval includes a non-intimate reporter. When there are a plurality of corresponding non-intimate reporters, the registration check box cb2 is provided for each of the non-intimate reporters.
  • the user checks the corresponding registration check box cb2 and operates the send button B1 provided in the approval request mail.
  • information for instructing registration of the checked reporter to the intimate reporter is returned to the recipe site server 31, and the recipe site server 31 performs processing for registering the corresponding reporter as the intimate reporter based on the information.
  • processing for the intimate information DB 35 processing is performed in which the user ID of the reporter that is the registration target is associated with the user ID of the corresponding receiver and stored.
  • the receiver can manually register the non-intimate reporter with the intimate reporter. Whether or not sufficient feeling of intimacy is felt may differ depending on the personality of the receiver and the contents of communication with the reporter, and there may be a case where sufficient intimacy is established even if there is little communication. For this reason, as the registration of the intimate reporter, not only automatic registration based on closeness but also manual registration is possible, so that the number of persons subject to automatic approval is expected to increase. Therefore, it is possible to increase the effect of suppressing the trouble related to the user's report approval.
  • the approval control processing unit F3 automatically performs an approval process with the passage of time after making an approval request for the created report posted by the intimate reporter.
  • the approval control processing unit F3 of this example executes the approval process for the created report according to the fact that the elapsed time from the date when the approval request for the created report is made has become a certain time or more.
  • the approval control processing unit F3 of this example turns off the approval flag Fa prepared for each created report as an automatic approval process as described above and an approval process based on the operation of the receiver (for example, “0”). To change from ON to ON (for example, “1”).
  • the approval flag Fa is information stored in the report DB 34 in association with each report ID.
  • the approval control processing unit F3 determines whether or not an unapproved report is an inappropriate report that is a report posted by an inappropriate reporter before requesting approval from the receiver. If it is determined that the report is inappropriate, the report is not requested for approval.
  • the user as an inappropriate reporter is managed by ON / OFF of the inappropriate flag Fi stored in the user DB 32 by the process of the inappropriate reporter determination processing unit F2 described above. If the inappropriate flag Fi associated with the user who posted the target report is ON, the approval control processing unit F3 determines that the report is an inappropriate report and excludes the report from the approval request. .
  • the approval control processing unit F3 adjusts the timing of requesting approval based on the result of analyzing the report approval behavior of the receiver in the past. Specifically, in this example, as the analysis of the above report approval behavior, the time required from the approval request to the approval of the past approved report of the receiver is analyzed. Specifically, for the past approved report of the receiver, the average value of the time required from the approval request to the approval is calculated, and the timing for requesting the approval is adjusted according to the size of the average value. In this example, the approval request timing is adjusted so that the approval request timing is advanced as the average value increases (that is, the approval tends to be delayed).
  • an approval request for an unapproved report for the posted recipe is made for each posted recipe in accordance with the following (Condition 1) or (Condition 2).
  • the number of unapproved reports is equal to or greater than a predetermined threshold (hereinafter referred to as “number threshold th”).
  • number threshold th The elapsed time from the posting date of the oldest unapproved report is equal to or longer than a predetermined threshold (hereinafter referred to as “time threshold TH”).
  • time threshold TH a predetermined threshold
  • the approval control processing unit F3 automatically sets a posting report by an intimate reporter having a closeness with a receiver as a certain degree or more.
  • the closeness evaluation processing unit F1 evaluates the closeness based on the “number of reporter past report approvals by the reporter” as described above, the reporter whose post report is not automatically approved is While posting a report to, the posting report is automatically approved.
  • the reporter can save the trouble of performing report approval for the reporter while repeating report approval for the same reporter, and in this respect, the burden on the approval of the reporter can be reduced.
  • FIG. 7 shows processing related to determination of an intimate reporter.
  • the recipe site server 31 waits until a creation report is posted in step S101. If the creation report is posted, the reporter and the recipe of the target recipe are specified in step S102. That is, the user ID is specified for each of a user as a reporter of a posted report and a recipe targeted by the report, in other words, a user as a reciper who has posted a recipe as a posting destination of the report.
  • step S103 following step S102 the recipe site server 31 specifies the number of report approvals to the reporter by the receiver. That is, based on the above-described approval history information stored in the user DB 32, the number of report approvals to the reporter in the past by the receiver is specified.
  • step S104 the recipe site server 31 determines whether or not the recipe has been posted to the reporter's posted recipe in the past. This determination can be made based on the aforementioned report posting history information and recipe posting history information stored in the user DB 32.
  • step S104 if the reporter has not posted a report to the reporter's posted recipe in the past, the recipe site server 31 proceeds to step S105, and calculates the closeness between the receiver and the reporter based on the specified number of times information. .
  • the report approval count specified in step S103 is handled as the familiarity. For this reason, the calculation process of step S105 can be made unnecessary.
  • step S106 the recipe site server 31 determines whether or not the familiarity is greater than or equal to the first intimacy threshold described above. If the familiarity is greater than or equal to the first intimacy threshold, the process proceeds to step S111. In close reporter registration process.
  • step S106 a process of storing the reporter user ID in the intimacy information DB 35 in association with the reporter user ID is performed. If it is determined in step S106 that the familiarity is not equal to or greater than the first intimacy threshold, the recipe site server 31 passes the process of step S111 and ends the process shown in FIG.
  • step S104 determines whether the reporter has posted a report for the reporter's posted recipe in the past. If it is determined in step S104 that the reporter has posted a report for the reporter's posted recipe in the past, the recipe site server 31 proceeds to step S107 and specifies the reporter's report posting count for the posted recipe by the reporter. .
  • the number of report postings can be specified based on report posting history information and recipe posting history information stored in the user DB 32.
  • step S108 following step S107 the recipe site server 31 specifies the number of report approvals to the receiver by the reporter. That is, the number of posting reports approved by the reporter among the posting reports of the recipe for the posting recipe by the reporter is specified.
  • step S109 the recipe site server 31 calculates the intimacy between the receiver and the reporter based on the specified number of times information, that is, the number of times information specified in steps S103, S107, and S108. Specifically, in this example, the total value of the specified number of times is calculated as the familiarity.
  • step S110 the recipe site server 31 determines whether or not the intimacy is equal to or greater than the second intimacy threshold described above. If the intimacy is equal to or greater than the second intimacy threshold, the process proceeds to step S111. Perform reporter registration processing. In response to the execution of the process of step S111, the recipe site server 31 ends the process shown in FIG.
  • step S110 if the closeness is not greater than or equal to the second closeness threshold value in step S110, the recipe site server 31 passes the process in step S111 and ends the process shown in FIG.
  • the calculation method of the familiarity is not limited to the above method.
  • a value obtained by adding or multiplying a numerical value corresponding to the number of approvals specified in step S108 to the number of report postings specified in step S107 is obtained, and the value is added to the number of report approvals specified in step S103.
  • FIG. 8 shows processing related to determination of an inappropriate reporter.
  • the process related to the determination of the inappropriate reporter is repeatedly performed on the time axis by, for example, batch processing based on the storage information in the report DB 34.
  • the recipe site server 31 sets the user identification value u to the start value uS.
  • the user identification value u is an identification value for identifying a user to be processed
  • the start value uS is set as a value for specifying a range (number of users) of users to be processed together with an end value uE to be described later. It is what is done.
  • step S202 the recipe site server 31 determines whether or not the number of creation report postings by the u-th user is n or more (n is a natural number of 2 or more). If the number of creation report postings by the u-th user is not n or more, the recipe site server 31 advances the process to step S209 described later. That is, in this example, the inappropriate reporter is determined based on the similarity between the images. Therefore, when it is predicted that a plurality of images required for the determination cannot be acquired, the inappropriate reporter determination described below is performed. The processing (S203 to S208) is passed.
  • step S202 when the number of creation report postings by the u-th user is n or more, the recipe site server 31 proceeds to step S203, determines whether there is a creation report with a different posting destination recipe, and the posting destination recipe is If there is no different creation report, the process proceeds to step S209.
  • step S203 if it is determined in step S203 that there is a creation report with a different posting destination recipe, the recipe site server 31 acquires a posted image of each creation report in step S204. That is, the posting image of each creation report as a creation report with a different posting destination recipe is acquired.
  • step S205 following step S204 the recipe site server 31 evaluates the similarity between images. That is, as described above, in this example, the degree of similarity between each acquired image and all other acquired images is calculated.
  • step S206 the recipe site server 31 determines whether there is an identical / similar image. As described above, in this example, images having a relationship of similarity of a certain value or more are specified as the same / similar images. If there is no identical / similar image, the recipe site server 31 advances the process to step S209. That is, in this case, the u-th user is not determined as an inappropriate reporter.
  • step S207 determines whether the number of identical / similar images is m or more (m is a natural number of 2 or more).
  • m is a natural number of 2 or more.
  • a plurality of sets can be specified as the same / similar images, and when a plurality of sets are specified as the same / similar images, that is, a plurality of the same / similar images are calculated.
  • step S207 it is determined whether or not the maximum number is m or more. If the number of identical / similar images is not greater than or equal to m, the recipe site server 31 advances the process to step S209.
  • the recipe site server 31 proceeds to step S208 and performs improper setting processing for the u-th user. That is, a process of turning on the inappropriate flag Fa associated with the user ID of the u-th user and stored in the user DB 32 is performed.
  • step S209 the recipe site server 31 determines whether or not the user identification value u is greater than or equal to the end value uE. This is equivalent to determining whether or not the target processing (the processing of steps S202 to S208) has been completed for all users within the processing target range set by the start value uS and the end value uE described above. To do. If the user identification value u is not equal to or greater than the end value uE, the recipe site server 31 proceeds to step S210, increments the user identification value u by 1, and then returns to step S202 described above. On the other hand, if the user identification value u is equal to or greater than the end value uE, the recipe site server 31 ends the process shown in FIG.
  • the process shown in FIG. 8 can be performed by excluding a user who has already been determined as an inappropriate reporter from the processing target.
  • FIG. 9 shows processing related to determination of a user who tends to be late.
  • the processing related to the determination of the user who tends to be delayed is repeatedly performed on the time axis by, for example, batch processing based on the above-described approval history information.
  • the recipe site server 31 sets the user identification value u to the start value uS in step S ⁇ b> 301, and then determines in step S ⁇ b> 302 whether the number of report approvals for the u-th user is multiple. If the report approval frequency of the u-th user is not a plurality of times, the recipe site server 31 advances the processing to step S308 described later.
  • the user who is lagging is judged based on the average value of the time from report posting to approval.
  • the process (S303 to S307) for determining a user having a tendency to delay, which will be described in the above, is not performed.
  • the recipe site server 31 proceeds to step S303, and calculates the time required from posting to approval for each approved report. That is, for each approved report of the u-th user specified based on the approval history information, the time required from report posting to approval is calculated.
  • the report posting date / time information of the approved report can be specified based on the report ID of the approved report and the report posting history information described above.
  • step S304 following step S303 the recipe site server 31 calculates an average value of the calculated times, and determines in step S305 whether the average value is equal to or greater than a predetermined value. If the average value is equal to or greater than the predetermined value, the recipe site server 31 executes processing for turning on the delay tendency flag Fd of the u-th user in step S306 and proceeds to step S308, and the average value must be equal to or greater than the predetermined value. For example, the recipe site server 31 executes a process of turning off the delay tendency flag Fd of the u-th user in step S307, and proceeds to step S308.
  • step S308 the recipe site server 31 determines whether or not the user identification value u is equal to or greater than the end value uE. If the user identification value u is not equal to or greater than the end value uE, the process proceeds to step S309 and the user identification value u is set. After incrementing by 1, the process returns to step S302. On the other hand, if the user identification value u is equal to or greater than the end value uE, the recipe site server 31 ends the process shown in FIG.
  • FIG. 10 shows processing related to the approval request.
  • the processing shown in FIG. 10 is also repeatedly performed on the time axis by, for example, batch processing.
  • the recipe site server 31 specifies a processing target receiver in step S401. That is, one receiver to be processed is specified from the receivers specified from the recipe posting history information described above.
  • the recipe site server 31 determines whether there is an unapproved report. That is, it is determined whether or not there is an unapproved report in the posted report for the posted recipe by the recipe specified in step S401. This determination can be made based on the report posting history information and the approval history information.
  • step S402 If it is determined in step S402 that there is no unapproved report, the recipe site server 31 finishes the process shown in FIG. That is, in this case, since there is no report that requires the receiver to approve, the process (S404 to S412) related to the approval request described below is not executed.
  • step S402 determines whether there is an unapproved report. That is, it is determined whether or not there is a report other than the inappropriate report in the unapproved report specified in step S402.
  • the inappropriate report is specified as a created report posted by a user whose inappropriate flag Fi is ON.
  • the non-approved report excluding the inappropriate report is referred to as “required approval request report”. If it is determined in step S403 that there is no approval request report, the recipe site server 31 ends the process shown in FIG.
  • step S403 determines whether there is a request for approval request report. If it is determined in step S403 that there is a request for approval request report, the recipe site server 31 proceeds to step S404, specifies the number of approval request reports required, and posts the oldest approval request report in step S405. Specify the date and time.
  • the posting date of the oldest approval request report is referred to as “oldest posting date”.
  • step 406 the recipe site server 31 determines whether or not the processing target receiver is a user who tends to be late. That is, it is determined whether or not the user has the delay tendency flag Fd ON. If the processing target receiver is not a delayed user, the recipe site server 31 proceeds to step S407, determines whether the number of approval request reports required is greater than or equal to the number threshold th1, and the number of approval request reports required must be greater than the number threshold th1. In step S408, it is determined whether the elapsed time from the oldest posting date is equal to or greater than the time threshold TH1. If the elapsed time from the oldest posting date / time is not equal to or greater than the time threshold TH1, the recipe site server 31 finishes the process shown in FIG. That is, in this case, since neither of (condition 1) and (condition 2) described above is satisfied, an approval request is not made.
  • step S407 If the number of approval request reports required in step S407 is greater than or equal to the threshold number th1, or if the elapsed time from the oldest posting date and time is greater than or equal to the time threshold value TH1 in step S408, the recipe site server 31 proceeds to step S411.
  • Approval request processing for approval request report is performed. That is, a process for transmitting an approval request mail requesting approval for an approval request report to a user as a processing target receiver is performed. At this time, as the approval request mail, an electronic mail in a format provided with the above-described check box cb1 is generated. If the approval request request report includes a post report from a non-intimate reporter for the processing target receiver, an e-mail is generated in a format provided with the registration check box cb2 for the corresponding reporter. .
  • the recipe site server 31 executes an approval request date storage process in step S412. That is, out of the created reports for which approval is requested in the process of step S411, the created report whose request for approval is the first time is targeted, the approval request date and time of the created report (for example, in step S411).
  • the process of storing the request process execution date and time) in the report DB 34 is performed.
  • the recipe site server 31 ends the process shown in FIG.
  • step S406 determines whether the processing target receiver is a delayed user
  • step S409 determines whether the number of approval request reports required is equal to or greater than the number threshold th2, and If the number of approval request reports is not equal to or greater than the number threshold th2, the process proceeds to step S410 to determine whether or not the elapsed time from the oldest posting date is equal to or greater than the time threshold TH2. If the elapsed time from the oldest posting date / time is not equal to or greater than the time threshold value TH2, the recipe site server 31 ends the process shown in FIG.
  • the number threshold th2 is smaller than the number threshold th1
  • the time threshold TH2 is smaller than the time threshold TH1.
  • step S409 If the number of approval request reports required in step S409 is equal to or greater than the number threshold th2, or if the elapsed time from the oldest posting date is equal to or greater than the time threshold TH2 in step S410, the recipe site server 31 requests the approval request in step S411. The processing is executed, and the storage processing of the approval request date and time in the subsequent step S412 is executed, and then the processing shown in FIG.
  • FIG. 11 shows processing related to automatic approval.
  • the processing shown in FIG. 11 is also repeatedly performed on the time axis by, for example, batch processing.
  • the recipe site server 31 performs a process of specifying a processing target receiver in step S ⁇ b> 501 and determines in step S ⁇ b> 502 whether there is an unapproved report.
  • the processes in steps S501 and S502 are the same as the processes in steps S401 and S402 described with reference to FIG.
  • step S502 If it is determined in step S502 that there is no unapproved report, the recipe site server 31 ends the process shown in FIG. That is, in this case, since there is no report that should be automatically approved, the process (S504 to S509) related to automatic approval described below is not executed.
  • step S502 determines whether there is an unapproved report. If it is determined in step S502 that there is an unapproved report, the recipe site server 31 proceeds to step S503, determines whether there is an approval request report required, and if it is determined that there is no approval request report, FIG. If it is determined that there is an approval request report, the process proceeds to step S504.
  • step S504 the recipe site server 31 identifies the number of approval request reports (hereinafter referred to as “D”), and in step S505, sets the processing target report identification value d to the initial value “0”.
  • the process target report identification value d is a value for identifying an approval request report that is a process target among approval request reports.
  • step S506 the recipe site server 31 determines whether the d-th report is a post report by an intimate reporter. This determination can be made based on the report ID of the d-th report, the storage information of the report DB 34, the user ID of the processing target receiver, and the storage information of the intimacy information DB 55. Specifically, the determination specifies the user ID of the posting reporter of the d th report based on the report ID of the d th report and the storage information of the report DB 34, and the specified user ID is stored in the storage information of the intimacy information DB 55. This is done by determining whether or not it is associated with the user ID of the processing target receiver.
  • step S506 If it is determined in step S506 that the d-th report is not a post report by an intimate reporter, the recipe site server 31 advances the process to step S510 described later. That is, in this case, automatic approval for the d-th report is not performed.
  • step S506 if it is determined in step S506 that the d-th report is a post report by an intimate reporter, the recipe site server 31 proceeds to step S507 and specifies an approval request date and time for the d-th report. Specifically, the approval request date and time associated with the report ID of the d-th report among the approval request date and time stored in the report DB 34 by the processing of the previous step S412 is specified.
  • step S508 the recipe site server 31 determines whether or not the elapsed time from the specified approval request date and time is equal to or longer than a predetermined time. If the elapsed time is not equal to or longer than the predetermined time, the process proceeds to step S510. If the elapsed time is equal to or longer than the predetermined time, the process proceeds to step S509 to perform an approval process for the d-th report. That is, the process of turning ON the approval flag Fa associated with the report ID of the d-th report in the report DB 34 is performed.
  • step S509 the recipe site server 31 determines whether or not the processing target report identification value d is equal to or greater than “D” described above, and the processing target report identification value d must be equal to or greater than “D” described above. For example, the process proceeds to step S511, and the process target report identification value d is incremented by 1. Then, the process returns to step S505. On the other hand, if the processing target report identification value d is equal to or greater than “D” described above, the recipe site server 31 ends the processing shown in FIG.
  • the posting report from the intimate reporter depends on the elapsed time from the approval request date and time. Automatic approval.
  • intimacy is, for example, a user ID (or user name, etc.) with a recipe site.
  • Evaluation can also be made using friendship information between users in SNS (Social Networking Service) in which user-identifiable information) is linked (information for managing users who are registered as friends).
  • SNS Social Networking Service
  • the recipe site server 31 can access information in a contact book (for example, a phone book or an e-mail address book) stored in a predetermined information processing apparatus such as the user terminal 4, the contact is made.
  • Intimacy can also be evaluated using information in the book. For example, the closeness is evaluated by using information on whether or not the name information of the target reporter is registered in the contact book information stored in the user terminal 4 used by the user as the receiver.
  • the evaluation of the information reliability of the posted report performed in the determination of the inappropriate reporter an example of performing the evaluation based on the similarity of the images used in the posted report is given, but as the evaluation of the information reliability,
  • the evaluation is not limited to the evaluation based on the similarity of images, and for example, the evaluation can be performed based on the matching degree of characters between the posting reports. For example, if there are a large number of created reports that have a certain degree of character matching or more, it is estimated that the target reporter is likely to use the same comment. It can be evaluated that information reliability is low.
  • an evaluation based on the length of time required from posting the target recipe to the target reporter (last browsing if the recipe is viewed multiple times) to posting the creation report for the recipe Can also be done. It can be evaluated that the more posted reports with a shorter time, the lower the information reliability of the posted report by the target reporter.
  • the approval request is made by e-mail
  • the approval request can also be made as a request on a specific web page at the recipe site, a request by a push notification to the user terminal 4, or the like.
  • requirement with respect to a receiver can also be made whenever the report posting with respect to the posting recipe by this receiver is performed.
  • the determination process for the inappropriate reporter can be performed each time a report is posted to the posting recipe by the receiver.
  • the information processing apparatus (recipe site server 31) according to the first embodiment is a user who has posted a report on a recipe submitted by a recipe and a recipe that is a user who has posted a recipe on a website that posts a recipe.
  • a familiarity evaluation unit (familiarity evaluation processing unit F1) that evaluates the familiarity with a certain reporter based on information associated with each of the receiver and the reporter is provided.
  • an intimate reporter who is a reporter with a certain degree of intimacy submits a report
  • the report according to the passage of time without manual approval from the receiver
  • an approval control unit (approval control processing unit F3).
  • the posting report of the intimate reporter is automatically approved as time elapses, it is possible to save time and effort for the approval of the receiver for these reports.
  • by performing automatic approval it is possible to suppress a decrease in the number of reports published.
  • the report by the non-intimate reporter is not subject to automatic approval, and manual approval by the receiver is required. For this reason, the deterioration of the quality of the posted report is suppressed.
  • requesting manual approval of a receiver in a report by a non-intimate reporter gives the receiver an opportunity to communicate with the non-intimate reporter. It is possible.
  • the promotion of communication in this way contributes to the improvement of intimacy between the receiver and the intimate reporter, and the report can be automatically approved the next time a report is posted from the intimate reporter. Increases nature. Increasing the possibility of automatic approval contributes to reducing the burden associated with the reporter's report approval.
  • the receiver and the reporter are able to simultaneously suppress the deterioration in the quality of the report publication page and the reduction in the number of report publications. Communication between them can be promoted.
  • the inappropriate reporter determination unit that determines whether or not the reporter is an inappropriate reporter based on the result of evaluating the information reliability of the report posted by the reporter in the past.
  • the approval control unit determines whether or not the report is an inappropriate report posted by the inappropriate reporter before requesting approval from the receiver for the unapproved report. However, if it is determined that the report is inappropriate, the report is not requested for approval.
  • the inappropriate reporter determination unit posts a report using the same or similar images to a plurality of recipes as to whether or not the reporter is an inappropriate reporter. Judgment based on whether or not.
  • the familiarity evaluation unit evaluates the familiarity based on the past number of report approvals for the reporter by the receiver.
  • the number of past report approvals for the reporter by the receiver functions as an index for estimating the frequency of communication between the two. Therefore, it is possible to appropriately evaluate the closeness between the two and automatically approve a reporter with a relatively high degree of intimacy. Further, a reporter whose posting report has not been automatically approved is designed to automatically approve the posting report while repeating the posting of the report to the receiver. In other words, the reporter can save the trouble of performing report approval for the reporter while repeating report approval for the same reporter, and in this respect, the burden on the approval of the reporter can be reduced.
  • the familiarity evaluation unit evaluates the familiarity based on the reporter's report posting count for the posting recipe by the reporter.
  • the number of reporter submissions for the recipe submitted by the reporter also functions as an index for estimating the communication frequency between the two. Therefore, it is possible to appropriately evaluate the closeness between the two and automatically approve a reporter with a relatively high degree of intimacy.
  • the familiarity evaluation unit evaluates the familiarity based on the number of approvals for the reporter posting report for the posting recipe by the reporter.
  • the approval control unit adjusts the timing for requesting approval based on the result of analyzing the report approval behavior of the receiver in the past.
  • the approval control unit when there are a plurality of unapproved reports as posting reports for the recipe recipe of the receiver, each unapproved report as a request for approval for the receiver.
  • a request is made in a format that allows an approval instruction operation.
  • the approval control unit makes a request in a format that allows the reporter's intimate reporter to perform a registration instruction operation as an approval request to the receiver.
  • Second Embodiment> [2-1. Approval control method as the second embodiment]
  • posting a posting report is performed under the condition of approval by the receiver and input of a reply from the receiver.
  • the configuration of the network system 1 is different in that a recipe site server 31A is provided instead of the recipe site server 31, and the other components are the same as those in the first embodiment. It is the same.
  • the parts that have already been described in the first embodiment are denoted by the same reference numerals and the same step numbers and are not described unless otherwise specified.
  • the recipe site server 31A differs from the recipe site server 31 in that it has an approval control processing unit F3A instead of the approval control processing unit F3.
  • the approval control processing unit F3A makes a request in a format that allows a reply input to an unapproved report as an approval request to the receiver. At this time, if there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, the approval control processing unit F3A makes a request in a format that allows a reply input to each unapproved report.
  • FIG. 13 shows an example of a transmission request mail corresponding to a case where there are a plurality of unapproved reports that should be requested for approval as a transmission request mail transmitted to the receiver by the approval control processing unit F3A.
  • the transmission request mail in this case is different from the transmission request mail shown in FIG. 6 in that a comment input field rp is provided for each unapproved report.
  • the comment input field rp is a field for inputting a reply comment for the corresponding unapproved report, and a user as a receiver can enter text in the comment input field rp.
  • the user can return the text information input in the comment input field rp to the recipe site server 31A as return information for the corresponding unapproved report by operating the transmission button B1 provided in the transmission request mail.
  • the approval control processing unit F3A performs control so that the report is posted on the recipe site on condition that the report is approved and a reply input from the receiver is performed.
  • the reply flag Fr is associated with the report flag of each created report that has been posted and registered in the report DB 34 together with the approval flag Fa described above.
  • ON for example, “1” indicates that the reply has been completed, and OFF (for example, “0”) indicates that the reply has not been made.
  • the reply flag Fr is stored for each report ID in the report DB 34.
  • both the approval flag Fa and the reply flag Fr are included in the posting reports. Only posting reports that are ON will be posted.
  • the approval control processing unit F3A automatically performs the approval processing according to the operation input of the receiver and the posting report of the intimate reporter in the same manner as the approval control processing unit F3 in the first embodiment. Approval processing is performed and the approval flag Fa is set to ON.
  • the approval control processing unit F3A responds to the comment input field rp when the reply information is input to the comment input field rp in the approval request mail as described above and the input reply information is received. Processing for turning on the reply flag Fr for the unapproved report to be performed is performed. As a result, a report that has been approved and for which a reply from the receiver has been input is posted on the recipe site.
  • the approval control processing unit F3A sends an approval request mail in a format in which a comment input field rp is provided for each approval request report. Generate and send.
  • the recipe site server 31A in the second embodiment executes the process shown in FIG. 14 is executed by the CPU 101 in the recipe site server 31A based on a program stored in a predetermined storage device such as the ROM 102 or the storage unit 108 in the recipe site server 31A.
  • the recipe site server 31A determines in step S601 whether or not there is a reply to the posted report. That is, the reply information to the transmission request mail transmitted in step S411, specifically, the input information to the transmission request mail received in response to the operation of the transmission button B1 in the transmission request mail is added to the comment input field rp. It is determined whether or not input information is included.
  • step S601 If it is determined in step S601 that there is no reply to the posted report, the recipe site server 31A ends the process shown in FIG. On the other hand, if it is determined in step S601 that there is a reply to the posted report, the recipe site server 31A proceeds to step S602 and performs a reply setting process for the corresponding report. That is, the created report corresponding to the comment input field rp for which the reception of the input information has been confirmed in step S601 is specified, and the reply flag Fr stored in the report DB 34 in association with the report ID of the specified created report is set. Processing to turn on is performed. In response to the execution of the process of step S602, the recipe site server 31A ends the process shown in FIG.
  • reply input input of standard reply information that is information in which the reply contents are standard contents is accepted. You can also.
  • standard reply information for example, information by an image such as a fixed sentence or a stamp can be cited.
  • the reply input can be received in a form such as accepting a selection input of arbitrary standard reply information from the receiver for a plurality of types of standard reply information presented to the receiver.
  • the receiver can complete the reply input to the posting report by inputting, for example, a standard sentence or a stamp. Therefore, it is possible to reduce the burden on the receiver when posting the posted report on the site.
  • the approval control unit is a report that is approved and a reply is input from the receiver. As a result, the report is controlled to be posted on the website.
  • the approval control unit when there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, each unapproved report as a request for approval for the receiver.
  • a request is made in a format that allows reply input to.
  • the approval control unit accepts input of standard reply information, which is information in which the reply content is a standard content, as a reply input.
  • the receiver can complete the reply input to the posted report by, for example, inputting a fixed sentence or a stamp, and can reduce the burden on the receiver when posting the posted report on the site.
  • the program according to the embodiment provides the intimacy between a reporter who is a user who has posted a recipe on a website for posting a recipe and a reporter who is a user who has posted a report on a recipe posted by the recipe, and the reporter and the reporter, respectively.
  • this program corresponds to a program that causes an information processing apparatus such as the recipe site server 31 to execute the processes described with reference to FIGS.
  • Such a program can be stored in advance in an HDD as a storage medium built in a device such as a computer device, a ROM in a microcomputer having a CPU, or the like. Alternatively, it can be stored (stored) temporarily or permanently in a removable storage medium such as a semiconductor memory, memory card, optical disk, magneto-optical disk, or magnetic disk. Such a removable storage medium can be provided as so-called package software. Further, such a program can be installed from a removable storage medium to a personal computer or the like, or can be downloaded from a download site via a network such as a LAN or the Internet.

Landscapes

  • Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The present invention promotes communication between recipe posters and report posters, by minimizing the burden on the recipe poster of acknowledging reports, while balancing suppression of a loss in quality of the report publication page and suppression of a decline in the number of reports published. To this end, this information processing device is equipped with a familiarity assessment unit for assessing the familiarity between a recipe poster, who is a user that contributed a recipe to a website where recipes are published, and a report poster, who is a user that contributed a report about the recipe contributed by the recipe poster, and an acknowledgement control unit which: when the report was contributed by a familiar report poster for which the degree of familiarity is no less than a set level, requests that the recipe poster acknowledge the report, and thereafter, executes report acknowledgement processing when time passes even if the recipe poster did not manually provide acknowledgement; and when the report was contributed by an unfamiliar report poster for which the degree of familiarity is less than the set level, requests that the recipe poster acknowledge the report, but does not execute report acknowledgement processing when time passes.

Description

情報処理装置、情報処理方法、プログラム、記憶媒体Information processing apparatus, information processing method, program, and storage medium
 本発明は、情報処理装置と情報処理方法、情報処理装置を実現するプログラム、及びプログラムを記憶した記憶媒体に関するものであり、特には、ウェブサイトに投稿されたレシピに対するレポートの承認に係る処理技術の分野に関する。 The present invention relates to an information processing apparatus and an information processing method, a program for realizing the information processing apparatus, and a storage medium storing the program, and in particular, a processing technique related to approval of a report for a recipe posted on a website. Related to the field.
 料理についてのレシピの投稿を受け付け、投稿されたレシピを掲載するウェブサイト(以下「レシピサイト」と表記)が広く知られている。各ユーザは、例えばサイト側で用意された所定の入力ページに対して使用食材や調味料といった材料情報や各材料の分量等の情報入力を行うことで、レシピを投稿できる。以下、レシピの投稿者を「レシパ」と表記する。 Websites that accept recipe submissions for dishes and post posted recipes (hereinafter referred to as “recipe sites”) are widely known. Each user can post a recipe by inputting information such as material information such as used ingredients and seasonings and the amount of each material on a predetermined input page prepared on the site side, for example. Hereinafter, the poster of the recipe is referred to as “Recipa”.
 また、レシピサイトにおいて各ユーザは、サイトを通じて提示されたレシピを閲覧し、該レシピに従って料理を作成することができる。さらに、レシピに従って料理を作成したユーザは、作成した料理についての感想やレシパに対するコメント等を「レポート」としてサイトに投稿することができる。以下、レポートの投稿者のことを「レポータ」と表記する。投稿されたレポートは、一般的に、レシパ側の承認を経た上でサイトに掲載される。
 なお、レシピサイトによっては、レポートの投稿に応じて投稿者にポイント等のインセンティブが付与されることがある。
In addition, each user at the recipe site can browse the recipe presented through the site and create a dish according to the recipe. Furthermore, the user who created the dish according to the recipe can post an impression about the created dish, a comment on the recipe, and the like as a “report” on the site. Hereinafter, report contributors are referred to as “reporters”. Submitted reports are generally posted on the site after receiving approval from the receiver.
Depending on the recipe site, an incentive such as a point may be given to the contributor depending on the posting of the report.
 さらに、レシピサイトにおいて、投稿されたレポートについてはレシパが返信コメントを入力することも可能とされている。 Furthermore, on the recipe site, it is also possible for the reciper to input reply comments for the submitted reports.
 なお、関連する従来技術については例えば下記特許文献1を挙げることができる。 In addition, about the related prior art, the following patent document 1 can be mentioned, for example.
特開2012-146106号公報JP 2012-146106 A
 ここで、レシピサイトにおいては、例えばサイトの利用促進等の目的のため、レポートの掲載ページをレシパとレポータとのコミュニケーションの場として発展させたいとの要望がある。
 しかし、レシパが投稿レポートについて承認を行うことは、特に人気レシパ(レシピの被閲覧数の多いレシパ)やレシピ投稿数の多いレシパ等にとっては負担となり、承認が滞りがちとなる虞がある。承認が滞ることは、レシパとレポータとの間のコミュニケーション機会の喪失に繋がる虞があり、望ましくない。
Here, in the recipe site, for example, for the purpose of promoting the use of the site, there is a demand to develop the report posting page as a place for communication between the receiver and the reporter.
However, the approval of the posting report by the receiver is particularly burdensome for popular receivers (recipers with a large number of recipes viewed), recipes with a large number of recipe postings, and the approval may be delayed. Delaying approval is undesirable because it may lead to loss of communication opportunities between the receiver and the reporter.
 この際、レポートをサイト側で自動承認することも考えられるが、際限なくレポートが承認されてしまうとレシパの意に反したレポートが掲載されたり、不十分な内容のレポートでもレポータにポイントが付与されてしまう等の問題が生じる虞がある。 In this case, it is possible to automatically approve the report on the site side, but if the report is approved indefinitely, a report against the intention of the receiver will be posted, or even a report with insufficient content will give points to the reporter There is a possibility that a problem such as that may occur.
 本発明は上記した事情に鑑み為されものであり、レシパのレポート承認に係る負担を抑えながら、レポート掲載ページの質悪化の抑制とレポート掲載数の低下抑制との両立を図りつつ、レシパとレポータとの間のコミュニケーション促進を図ることを目的とする。 The present invention has been made in view of the above-mentioned circumstances, and while reducing the burden on the reporter's report approval, the receiver and the reporter are able to simultaneously suppress the deterioration of the quality of the report publication page and the reduction in the number of report publications. The purpose is to promote communication with each other.
 本発明に係る情報処理装置は、レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価部と、前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御部と、を備えるものである。 The information processing apparatus according to the present invention provides the intimacy between a reporter who is a user who has posted a recipe on a website for posting a recipe and a reporter who is a user who has posted a report on a posted recipe by the receiver. When an intimacy evaluation unit that evaluates based on information associated with each reporter and an intimacy reporter that is a reporter with a certain degree of intimacy or more, submits the report, the reporter is requested to approve the report. After that, even if there is no manual approval from the receiver, the report approval process is performed according to the passage of time, and when a non-intimate reporter that is a reporter whose intimacy is not more than the predetermined level has posted a report, While requesting approval for the report, do not perform report approval processing over time A certification control unit, in which comprises a.
 本発明によると、親密レポータの投稿レポートは時間経過に応じて自動承認されるため、それらのレポートについてレシパの承認の手間が省かれる。また、自動承認を行っていることで、レポートの掲載数の低下抑制を図ることが可能とされる。
 また、本発明では、非親密レポータによるレポートは自動承認の対象外とされており、レシパによる手動承認が要求される。このため、掲載レポートの質悪化の抑制が図られる。
 さらに、上記のように非親密レポータによるレポートにレシパの手動承認を要求していることは、レシパに非親密レポータとのコミュニケーション機会を与えていることになるため、両者のコミュニケーション促進を図ることが可能とされる。そして、このようにコミュニケーション促進が図られることは、レシパと非親密レポータとの間の親密度向上に寄与し、次回に非親密レポータからレポート投稿があった際に当該レポートが自動承認される可能性が高まる。自動承認される可能性が高まることは、レシパのレポート承認に係る負担抑制に寄与するものである。
According to the present invention, the posting report of the intimate reporter is automatically approved as time elapses, so that it is possible to save the trouble of approving the reporter for those reports. In addition, by performing automatic approval, it is possible to suppress a decrease in the number of reports published.
In the present invention, the report by the non-intimate reporter is not subject to automatic approval, and manual approval by the receiver is required. For this reason, the deterioration of the quality of the posted report is suppressed.
Furthermore, as described above, requesting manual approval of a receiver in a report by a non-intimate reporter gives the receiver an opportunity to communicate with the non-intimate reporter. It is possible. In addition, the promotion of communication in this way contributes to the improvement of intimacy between the receiver and the intimate reporter, and the report can be automatically approved the next time a report is posted from the intimate reporter. Increases nature. Increasing the possibility of automatic approval contributes to reducing the burden associated with the reporter's report approval.
 上記した本発明に係る情報処理装置においては、前記レポータが過去に投稿したレポートについての情報信頼度を評価した結果に基づき、前記レポータが不適レポータであるか否かを判定する不適レポータ判定部を備え、前記承認制御部は、未承認の前記レポートについて前記レシパに承認を要求する前に、当該レポートが前記不適レポータにより投稿されたレポートである不適レポートか否かを判定し、前記不適レポートであると判定した場合は当該レポートについての承認を要求しないことが可能である。 In the information processing apparatus according to the present invention described above, an inappropriate reporter determination unit that determines whether or not the reporter is an inappropriate reporter based on a result of evaluating information reliability of a report posted by the reporter in the past. The approval control unit determines whether the report is an inappropriate report that is a report posted by the inappropriate reporter before requesting the receiver to approve the unapproved report. If it is determined that there is, it is possible not to request approval for the report.
 これにより、レシパが未承認のレポートのうちシステム側で事前に不適と判定されたレポータのレポートは承認が要求されない。このため、当該レポートについてレシパによる承認の手間が省かれる。 ∙ As a result, reporter reports that are determined to be inappropriate by the system in advance are not required to be approved. This eliminates the need for approval by the receiver for the report.
 上記した本発明に係る情報処理装置においては、前記不適レポータ判定部は、前記不適レポータであるか否かを、前記レポータが同一又は類似画像を用いたレポートを複数のレシピに対して投稿しているか否かに基づき判定することが可能である。 In the information processing apparatus according to the present invention described above, the inappropriate reporter determination unit posts a report using the same or similar images to a plurality of recipes as to whether or not the reporter is the inappropriate reporter. It is possible to determine based on whether or not there is.
 これにより、レポートについての情報信頼度の評価として、レシピに対するレポートに適した評価を行うことが可能とされる。 This makes it possible to perform an evaluation suitable for the report for the recipe as an evaluation of the information reliability of the report.
 上記した本発明に係る情報処理装置においては、前記親密度評価部は、前記レシパによる前記レポータに対する過去のレポート承認回数に基づき前記親密度を評価するが可能である。 In the information processing apparatus according to the present invention described above, the closeness evaluation unit can evaluate the closeness based on the number of past report approvals to the reporter by the receiver.
 レシパによるレポータに対する過去のレポート承認回数は、両者の間のコミュニケーション頻度を推し量る指標として機能する。
 また、投稿レポートが自動承認されなかったレポータは、前記レシパへのレポート投稿を繰り返すうちに、その投稿レポートが自動承認されるように図られる。換言すれば、レシパは、同一レポータに対してレポート承認を繰り返すうち該レポータに対するレポート承認を行う手間が省かれるようになる。
The number of past report approvals for the reporter by the receiver functions as an index for estimating the frequency of communication between the two.
Further, a reporter whose posting report has not been automatically approved is designed to automatically approve the posting report while repeating the posting of the report to the receiver. In other words, the reporter saves time and effort to approve the report for the same reporter while repeating report approval for the same reporter.
 上記した本発明に係る情報処理装置においては、前記親密度評価部は、前記レポータによる投稿レシピに対する前記レシパのレポート投稿回数に基づき前記親密度を評価することが可能である。 In the information processing apparatus according to the present invention described above, the closeness evaluation unit can evaluate the closeness based on the reporter's report posting count for the posting recipe by the reporter.
 レポータによる投稿レシピに対するレシパのレポート投稿回数としても、両者の間のコミュニケーション頻度を推し量る指標として機能する。 ∙ The number of reporter submissions for the recipe submitted by the reporter also serves as an index for estimating the frequency of communication between the two.
 上記した本発明に係る情報処理装置においては、前記親密度評価部は、前記レポータによる投稿レシピに対する前記レシパの投稿レポートについての承認回数に基づき前記親密度を評価することが可能である。 In the information processing apparatus according to the present invention described above, the closeness evaluation unit can evaluate the closeness based on the number of approvals for the posting report of the receiver for the posting recipe by the reporter.
 これにより、レシパとレポータとの間の親密度がより適切に評価される。 This will allow the intimacy between the receiver and reporter to be more appropriately evaluated.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、前記レシパの過去におけるレポート承認行動を分析した結果に基づき、前記承認を要求するタイミングを調整するが可能である。 In the information processing apparatus according to the present invention described above, the approval control unit can adjust the timing for requesting the approval based on the analysis result of the report approval behavior of the receiver in the past.
 これにより、例えばレポートへの承認が遅滞傾向にあるレシパには早めに承認を要求する等、レシパによるレポート承認行動の特性に応じた適切なタイミングにより承認要求を行うことが可能とされる。 This makes it possible to make an approval request at an appropriate timing according to the characteristics of the report approval action by the receiver, such as requesting an earlier approval from a receiver whose approval to the report is delayed.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、前記レシパの投稿レシピに対する投稿レポートとして複数の未承認レポートがある場合は、前記レシパに対する承認の要求として、個々の未承認レポートに対する承認指示操作が可能な形式による要求を行うことが可能である。 In the information processing apparatus according to the present invention described above, when there are a plurality of unapproved reports as posting reports for the recipe recipe of the receiver, the approval control unit is configured to request individual approval reports for the receiver. It is possible to make a request in a format in which an approval instruction operation can be performed.
 これにより、レシパによるレポート承認の容易性が増す。 This increases the ease of report approval by the receiver.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、前記レシパに対する承認の要求として前記レポータの前記親密レポータへの登録指示操作が可能な形式による要求を行うことが可能である。 In the information processing apparatus according to the present invention described above, the approval control unit can make a request in a format that allows the reporter to perform a registration instruction operation to the intimate reporter as an approval request for the receiver.
 これにより、レシパは非親密レポータを手動により親密レポータに登録することが可能とされる。
 十分な親密性を感じるか否かはレシパ個人の性格やレポータとのコミュニケーション内容等の条件で異なり得るものであり、コミュニケーションが僅かであっても十分な親密性が築かれるケースも想定され得る。このため、親密レポータの登録として、親密度に基づく自動登録のみでなく手動登録が可能とされることで、自動承認の対象者数の増加が見込まれる。
This enables the receiver to manually register the non-intimate reporter with the intimate reporter.
Whether or not sufficient feeling of intimacy is felt may differ depending on the personality of the receiver and the contents of communication with the reporter, and there may be a case where sufficient intimacy is established even if there is little communication. For this reason, as the registration of the intimate reporter, not only automatic registration based on closeness but also manual registration is possible, so that the number of persons subject to automatic approval is expected to increase.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、承認され且つ前記レシパからの返信入力が行われたレポートであることを条件に、前記レポートが前記ウェブサイトに掲載されるように制御を行うが可能である。 In the information processing apparatus according to the present invention described above, the approval control unit may be posted on the website on condition that the report is approved and a reply is input from the receiver. It is possible to control.
 これにより、投稿レポートを掲載させるにあたり、レシパはレポートに対する返信という形式でのコミュニケーションをレポータに対してとることが必須とされる。 This makes it necessary for the reporter to communicate with the reporter in the form of a reply to the report when posting the posted report.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、前記レシパの投稿レシピに対する投稿レポートに複数の未承認レポートがある場合は、前記レシパに対する承認の要求として、個々の未承認レポートに対する前記返信入力が可能な形式による要求を行うことが可能である。 In the information processing apparatus according to the present invention described above, when there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, the approval control unit is configured as an individual unapproved report as a request for approval for the receiver. It is possible to make a request in a format in which the reply can be input.
 これにより、投稿レポートに対する返信入力の容易性が増す。 This will make it easier to input a reply to the posted report.
 上記した本発明に係る情報処理装置においては、前記承認制御部は、前記返信入力として、返信内容が定型の内容とされた情報である定型返信情報の入力を受け付けることが可能である。 In the information processing apparatus according to the present invention described above, the approval control unit can accept input of fixed reply information, which is information in which the reply content is set to a fixed content, as the reply input.
 これによりレシパは、投稿レポートへの返信入力を例えば定型文やスタンプ等の入力で済ませることが可能とされる。 This makes it possible for the receiver to input the reply to the post report by inputting, for example, a fixed phrase or a stamp.
 また、本発明に係る情報処理方法は、レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価ステップと、前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御ステップと、を情報処理装置が実行する情報処理方法である。
 このような情報処理方法によっても、上記した本発明に係る情報処理装置と同様の作用が得られる。
In addition, the information processing method according to the present invention provides a degree of intimacy between a reporter who is a user who has posted a recipe on a website posting a recipe and a reporter who is a user who has posted a report on a recipe posted by the receiver. , An intimacy evaluation step that evaluates based on information associated with each reporter, and an intimate reporter that is a reporter with an intimacy greater than a certain degree posts the report, the reporter approves the report After requesting, the report approval process is performed according to the passage of time without manual approval from the receiver, and when a non-intimate reporter who is a reporter whose intimacy is not the predetermined level or more submits a report, While requesting the reporter to approve the report, report approval processing over time And admission control step is not performed, which is a processing method of an information processing apparatus executes.
Also by such an information processing method, an operation similar to that of the information processing apparatus according to the present invention described above can be obtained.
 さらに、本発明に係るプログラムは、上記情報処理方法として実行する処理を情報処理装置に実行させるプログラムである。
 さらにまた、本発明に係る記憶媒体は、上記プログラムを記憶した記憶媒体である。これらのプログラムや記憶媒体により上記の情報処理装置を実現する。
Furthermore, a program according to the present invention is a program that causes an information processing apparatus to execute processing executed as the information processing method.
Furthermore, a storage medium according to the present invention is a storage medium storing the program. The above information processing apparatus is realized by these programs and storage media.
 本発明によれば、レシパのレポート承認に係る負担を抑えながら、レポート掲載ページの質悪化の抑制とレポート掲載数の低下抑制との両立を図りつつ、レシパとレポータとの間のコミュニケーション促進を図ることができる。 According to the present invention, while reducing the burden associated with the reporter's report approval, the communication between the receiver and the reporter is promoted while at the same time suppressing the deterioration in the quality of the report publication page and the reduction in the number of report publications. be able to.
第1の実施の形態のネットワークシステムの例を示した図である。It is the figure which showed the example of the network system of 1st Embodiment. レポートの掲載例を示した図である。It is the figure which showed the publication example of the report. 実施の形態のネットワークシステムを構成するコンピュータ装置のハードウェア構成を示したブロック図である。It is the block diagram which showed the hardware constitutions of the computer apparatus which comprises the network system of embodiment. 第1の実施の形態としての承認制御手法に係る機能をブロック化して示した機能ブロック図である。It is the functional block diagram which blocked and showed the function which concerns on the approval control method as 1st Embodiment. 親密情報DB(データベース)の記憶情報の例を示した図である。It is the figure which showed the example of the memory | storage information of intimacy information DB (database). 第1の実施の形態における承認要求についての説明図である。It is explanatory drawing about the approval request | requirement in 1st Embodiment. 親密レポータの判定に係る処理のフローチャートである。It is a flowchart of the process which concerns on determination of an intimate reporter. 不適レポータの判定に係る処理のフローチャートである。It is a flowchart of the process which concerns on determination of an unsuitable reporter. 遅滞傾向ユーザの判定に係る処理のフローチャートである。It is a flowchart of the process which concerns on a delay tendency user's determination. 承認要求に係る処理のフローチャートである。It is a flowchart of the process which concerns on an approval request. 自動承認に係る処理のフローチャートである。It is a flowchart of the process which concerns on automatic approval. 第2の実施の形態としての承認制御手法に係る機能をブロック化して示した機能ブロック図である。It is the functional block diagram which block-ized and showed the function which concerns on the approval control technique as 2nd Embodiment. 第2の実施の形態における承認要求についての説明図である。It is explanatory drawing about the approval request | requirement in 2nd Embodiment. 第2の実施の形態としての承認制御手法を実現するための処理を示したフローチャートである。It is the flowchart which showed the process for implement | achieving the approval control method as 2nd Embodiment.
 以下、実施の形態を次の順序で説明する。
<1.第1の実施の形態>
[1-1.ネットワークシステムの概要]
[1-2.コンピュータ装置のハードウェア構成]
[1-3.第1の実施の形態としての承認制御手法]
[1-4.処理手順]
[1-5.第1の実施の形態のまとめ]
<2.第2の実施の形態>
[2-1.第2の実施の形態としての承認制御手法]
[2-2.処理手順]
[2-3.第2の実施の形態のまとめ]
<3.プログラム及び記憶媒体>
<4.変形例>
Hereinafter, embodiments will be described in the following order.
<1. First Embodiment>
[1-1. Overview of network system]
[1-2. Hardware configuration of computer device]
[1-3. Approval control method as the first embodiment]
[1-4. Processing procedure]
[1-5. Summary of First Embodiment]
<2. Second Embodiment>
[2-1. Approval control method as the second embodiment]
[2-2. Processing procedure]
[2-3. Summary of Second Embodiment]
<3. Program and Storage Medium>
<4. Modification>
<1.第1の実施の形態>
[1-1.ネットワークシステムの概要]

 図1に、本実施の形態で前提とするネットワークシステム1の例を示す。
 ネットワークシステム1においては、例えばインターネットとしてのネットワーク2を介して、レシピサイト運営システム3におけるレシピサイトサーバ31と複数のユーザ端末4のそれぞれが互いに通信可能とされている。
<1. First Embodiment>
[1-1. Overview of network system]

FIG. 1 shows an example of a network system 1 assumed in the present embodiment.
In the network system 1, for example, the recipe site server 31 and the plurality of user terminals 4 in the recipe site operating system 3 can communicate with each other via a network 2 as the Internet.
 ユーザ端末4は、ウェブブラウザを備えたコンピュータ装置である。ユーザ端末4としては、例えば高機能携帯電話機(スマートフォン)や携帯電話機、携帯情報端末(タブレット端末)、携帯型又は据置型のパーソナルコンピュータ(PC)などが挙げられるが、ユーザ端末4の種類はこれらに限定されない。
 ユーザ端末4は、HTTP(Hypertext Transfer Protocol)要求をレシピサイト運営システム3におけるレシピサイトサーバ31等に送信することでウェブページや所定の処理を要求する。またユーザ端末4は、HTTP要求に応じて送られてきたウェブページデータ(例えばHTML(HyperText Markup Language)データ等)を受信し、該ウェブページデータに基づいてウェブブラウザによりウェブページの表示処理を行う。これにより、ユーザは所望のウェブページを閲覧したり操作したりすることができる。
The user terminal 4 is a computer device provided with a web browser. Examples of the user terminal 4 include a high-function mobile phone (smart phone), a mobile phone, a portable information terminal (tablet terminal), and a portable or stationary personal computer (PC). It is not limited to.
The user terminal 4 requests a web page or predetermined processing by transmitting an HTTP (Hypertext Transfer Protocol) request to the recipe site server 31 or the like in the recipe site operating system 3. The user terminal 4 receives web page data (for example, HTML (HyperText Markup Language) data) sent in response to the HTTP request, and performs a web page display process by the web browser based on the web page data. . Thereby, the user can browse and operate a desired web page.
 レシピサイト運営システム3は、それぞれコンピュータ装置で構成されたレシピサイトサーバ3a、ユーザDB(データベース)32、レシピDB33、レポートDB34、及び親密情報DB35を備えている。これらの各装置は、例えばLAN(Local Area Network)等のネットワークを介して互いに通信可能とされている。 The recipe site management system 3 includes a recipe site server 3a, a user DB (database) 32, a recipe DB 33, a report DB 34, and an intimacy information DB 35, each of which is constituted by a computer device. Each of these devices can communicate with each other via a network such as a LAN (Local Area Network).
 レシピサイトサーバ31は、料理のレシピの投稿受け付けやレシピの提示が行われるウェブサイトであるレシピサイトに関する各種処理を行う情報処理装置である。
 また、ユーザDB32には、レシピサイトを利用するユーザに関する各種の情報が記憶される。
The recipe site server 31 is an information processing apparatus that performs various processes related to a recipe site, which is a website where a recipe for posting a recipe for cooking and a recipe are presented.
The user DB 32 stores various types of information related to users who use the recipe site.
 ここで、ユーザは、レシピサイトを利用するにあたり、レシピサイト運営システム3に会員登録を行うことができる。会員登録の際にユーザは、ユーザID(ユーザ識別情報)、パスワード、氏名、メールアドレスなどの連絡先情報等、必要情報を登録する。ユーザは、登録したユーザID及びパスワードによりレシピサイトにログインすることで、レシピサイトが提供する要ログインの各種サービスを受けることができる。例えば、以下で説明するレシピの投稿やレシピに対する作成レポートの投稿等である。 Here, the user can register as a member in the recipe site management system 3 when using the recipe site. When registering a member, the user registers necessary information such as contact information such as a user ID (user identification information), a password, a name, and an e-mail address. The user can receive various services required for login provided by the recipe site by logging in to the recipe site using the registered user ID and password. For example, posting a recipe described below, posting a creation report for a recipe, and the like.
 ユーザDB32には、会員としてのユーザに係る各種の情報がユーザIDごとに記憶されている。ユーザDB32には、ユーザに係る情報として上記の必要情報が記憶されている。さらに、ユーザDB32には、レシピの閲覧やお気に入りレシピの登録等、レシピサイトにおけるユーザの各種行動履歴に係る情報(以下「行動履歴情報」と表記)等も記憶されている。
 なお、本例における行動履歴情報については後述する。
In the user DB 32, various types of information related to users as members are stored for each user ID. The user DB 32 stores the necessary information as information related to the user. Further, the user DB 32 also stores information (hereinafter referred to as “behavior history information”) related to various behavior histories of the user at the recipe site, such as recipe browsing and favorite recipe registration.
The action history information in this example will be described later.
 レシピサイトサーバ31は、ユーザ端末4から送られてきたHTTP要求に基づいて様々な処理を行う。例えば、レシピの投稿受け付けを行うためのウェブページをユーザに提示し、該ウェブページへの入力情報に基づいてレシピ情報(レシピの内容を示す情報)をレシピDB33に登録する処理を行う。 The recipe site server 31 performs various processes based on the HTTP request sent from the user terminal 4. For example, a web page for accepting submission of a recipe is presented to the user, and recipe information (information indicating the contents of the recipe) is registered in the recipe DB 33 based on information input to the web page.
 レシピ情報は、例えばレシピ名、料理ID、ジャンル、人数、使用食材とその分量、使用調味料とその分量、調理手順、及び料理画像の各情報で構成される。
 なお、料理IDは、レシピ情報に従って作成される料理を識別するための識別子である。また、ジャンルの情報は、料理が属するジャンルの情報であり、例えば「肉料理」「魚料理」「サラダ」「飲み物」等の各種分類が挙げられる。人数の情報は、レシピ情報に従って作成される対象料理が何人前であるかを表す情報とされる。また料理画像は、完成状態の料理を表すべき画像であり、例えばユーザによる投稿画像が用いられる。
The recipe information includes, for example, information on a recipe name, a cooking ID, a genre, the number of people, used ingredients and their amounts, used seasonings and their amounts, cooking procedures, and cooking images.
The dish ID is an identifier for identifying a dish created according to the recipe information. The genre information is genre information to which the dish belongs, and includes various classifications such as “meat dish”, “fish dish”, “salad”, and “drink”, for example. The information on the number of persons is information indicating how many servings the target dish created according to the recipe information. Further, the dish image is an image that should represent the finished dish, and for example, a posted image by the user is used.
 投稿されたレシピには、レシピを一意に特定可能とするための識別子であるレシピIDが割り付られ、レシピ情報は該レシピIDと対応づけられて(紐付けられて)レシピDB33に記憶される。 The posted recipe is assigned a recipe ID, which is an identifier for uniquely identifying the recipe, and the recipe information is associated with (associated with) the recipe ID and stored in the recipe DB 33. .
 ここで、以下、レシピを投稿したユーザのことを「レシパ」と表記する。 Hereafter, the user who posted the recipe is referred to as “Recipa”.
 レシピサイトサーバ31は、レシピDB33の記憶情報に基づき、レシピサイト上にレシピを掲載する処理を行う。具体的に、本例のレシピサイトサーバ31は、ユーザによって指定された検索キーワード等の検索条件に基づきレシピの検索処理を行い、検索条件に合致したレシピを掲載したウェブページをユーザに提示する処理を行う。 The recipe site server 31 performs processing for posting a recipe on the recipe site based on the storage information of the recipe DB 33. Specifically, the recipe site server 31 of this example performs a recipe search process based on a search condition such as a search keyword specified by the user, and presents a web page on which a recipe that matches the search condition is presented to the user I do.
 また、レシピサイトサーバ31は、レシピ情報に従って料理を作成したユーザより、作成レポートの投稿受け付けを行う。作成レポートは、レシピごとに投稿可能な情報とされ、例えば料理を作成した感想やレシパに対するコメント等の情報を含むべき情報とされている。本実施の形態では、作成レポートとしてはテキスト情報のみでなく、作成した料理を表す画像の投稿も可能とされている。
 レシピサイトサーバ31は、作成レポートの投稿受け付けを行うためのウェブページをユーザに提示し、該ウェブページへの入力情報に基づいて作成レポートをレポートDB34に登録する処理を行う。
In addition, the recipe site server 31 accepts submission of a creation report from the user who created the dish according to the recipe information. The creation report is information that can be posted for each recipe. For example, the creation report is information that should include information such as an impression of creating a dish and a comment on a recipe. In the present embodiment, as a creation report, not only text information but also an image representing the created dish can be posted.
The recipe site server 31 presents the user with a web page for accepting submission of a creation report, and performs processing for registering the creation report in the report DB 34 based on information input to the web page.
 投稿された作成レポートには、作成レポートを一意に特定可能とするための識別子であるレポートIDが割り付られる。レシピサイトサーバ31は、投稿された作成レポートの情報と投稿者のユーザIDとをレポートIDと対応づけてレポートDB34に記憶させる。 A report ID, which is an identifier for uniquely identifying the created report, is assigned to the posted created report. The recipe site server 31 stores information on the created report and the user ID of the poster in the report DB 34 in association with the report ID.
 以下、作成レポートを投稿したユーザのことを「レポータ」と表記する。 Hereafter, the user who posted the creation report is referred to as “reporter”.
 また、レシピサイトサーバ31は、投稿された作成レポートに対するレシパからの返信コメントの入力を受け付ける。さらに、レシピサイトサーバ31は、返信コメントに対するレポータからのコメントの入力を受け付ける。
 レシピサイトサーバ31は、これらレシパからの返信コメントや返信コメントに対するレポータによるコメントの入力があった場合は、入力された返信コメントや返信コメントに対するコメントの情報を、該当する作成レポートのレポートIDと対応づけてレポートDB34に記憶させる。
In addition, the recipe site server 31 receives an input of a reply comment from the receiver for the created creation report. Furthermore, the recipe site server 31 receives an input of a comment from a reporter for a reply comment.
When there is an input of a reply comment or reply comment from the reporter by the reporter, the recipe site server 31 corresponds the input reply comment or comment information for the reply comment with the report ID of the corresponding creation report. Then, it is stored in the report DB 34.
 図2は、作成レポートの掲載例を示した図である。
 本例では、或るレシピに対して投稿された作成レポートは、該レシピの掲載ページにおいて掲載される。以下、レシピの掲載ページのことを「レシピページ」と表記する。
 レシピページには、例えば上述したレシピの検索処理等を経てユーザにより指定されたレシピに対応するレシピ情報が掲載される。具体的に、この場合のレシピページには、レシピ情報を掲載する領域として、レシピ名の情報が掲載されるレシピ名掲載領域Ar1、料理写真が掲載される料理写真掲載領域Ar2、使用材料とその分量に関する情報として使用食材、使用調味料及びそれらの分量の情報がそれぞれ掲載される材料・分量掲載領域Ar3、調理手順の情報が掲載される調理手順掲載領域Ar4が設けられている。さらに、この場合のレシピページには、当該レシピページの掲載レシピに対して投稿された作成レポートが掲載されるレポート掲載領域Ar5が設けられている。
FIG. 2 is a diagram showing an example of the creation report.
In this example, a creation report posted for a recipe is posted on the recipe posting page. Hereinafter, a recipe posting page is referred to as a “recipe page”.
On the recipe page, for example, recipe information corresponding to a recipe designated by the user through the above-described recipe search process or the like is posted. Specifically, the recipe page in this case includes recipe name information area Ar1 in which recipe name information is posted, dish photo posting area Ar2 in which dish photos are posted, and ingredients used, as recipe information information areas. As information on the amount, there are provided a material / quantity posting area Ar3 in which used ingredients, used seasonings and information on their quantities are respectively posted, and a cooking procedure posting area Ar4 in which information on cooking procedures is posted. Further, the recipe page in this case is provided with a report posting area Ar5 in which a creation report posted for the posted recipe on the recipe page is posted.
 レポート掲載領域Ar5においては、複数の作成レポートを掲載可能とされている。個々の作成レポートの掲載領域においては、投稿された写真画像、及びテキストを掲載する領域が設けられていると共に、レシパからの返信コメントや該返信コメントに対するレポータからのコメントの入力があった場合には、それらのコメント情報の提示を指示するためのボタン(図中「その他のコメントを見る」)が提示される。 In the report posting area Ar5, a plurality of created reports can be posted. In the posting area of each created report, there is an area for posting posted photo images and text, and when there is a reply comment from a receiver and a comment input from a reporter for the reply comment Is provided with a button (“view other comments” in the figure) for instructing presentation of the comment information.
 ここで、投稿された作成レポートは、本実施の形態ではレシパによる承認を受けたことを条件としてレシピページに掲載される。なお、本例のレシピページは、作成レポートが掲載されるという意味で、レポート掲載ページとも換言できる。 Here, the created creation report is posted on the recipe page under the condition that it is approved by the receiver in this embodiment. In addition, the recipe page of this example can also be called a report posting page in the sense that a creation report is posted.
 図1に戻り、ユーザDB32には、上述した行動履歴情報として、先に例示したレシピの閲覧等の行動についての履歴情報の他、レシピの投稿や作成レポートの投稿、レシパによる作成レポートの承認、及び作成レポートへのレシパによる返信といった各種行動についての履歴情報が記憶される。本例では、これら各種行動についての行動履歴情報は、レシピサイトサーバ31がユーザの行動を監視した結果に基づきユーザDB32に記憶させる。 Returning to FIG. 1, in the user DB 32, as the above-described behavior history information, in addition to the history information about the behavior such as browsing the recipe exemplified above, the posting of the recipe, the creation report, the approval of the creation report by the receiver, In addition, history information about various actions such as a reply to the created report by the receiver is stored. In this example, the action history information regarding these various actions is stored in the user DB 32 based on the result of the recipe site server 31 monitoring the user's actions.
 具体的に、レシピサイトサーバ31は、レシピ閲覧履歴情報については、ユーザが閲覧したレシピのレシピIDを該ユーザのユーザIDと対応づけて記憶させる。また、レシピ投稿履歴情報については、ユーザが投稿したレシピのレシピIDを該ユーザのユーザIDと対応づけて記憶させ、レポート投稿履歴情報についてはユーザが投稿した作成レポートのレポートID、及び該作成レポートの投稿先レシピのレシピIDを該ユーザのユーザIDと対応づけて記憶させる。
 さらに、承認履歴情報については、ユーザが承認を行った作成レポートのレポートIDと、該作成レポートを投稿したレポータのユーザIDとを該ユーザのユーザIDと対応づけて記憶させ、レポートへの返信履歴情報についてはユーザが返信コメントの入力を行った作成レポートのレポートIDを該ユーザのユーザIDと対応づけて記憶させる。
 なお、上記のレシピ閲覧履歴情報、レシピ投稿履歴情報、レポート投稿履歴情報、承認履歴情報、返信履歴情報等、ユーザDB32に記憶される各行動履歴情報には、ユーザが該当する行動を行った日時の情報も記憶される。
Specifically, for the recipe browsing history information, the recipe site server 31 stores the recipe ID of the recipe viewed by the user in association with the user ID of the user. For recipe posting history information, the recipe ID of the recipe posted by the user is stored in association with the user ID of the user, and for report posting history information, the report ID of the created report posted by the user, and the created report The recipe ID of the posting destination recipe is stored in association with the user ID of the user.
Further, for the approval history information, the report ID of the created report approved by the user and the user ID of the reporter who posted the created report are stored in association with the user ID of the user, and the reply history to the report is stored. For the information, the report ID of the created report for which the user has input a reply comment is stored in association with the user ID of the user.
In addition, each action history information stored in the user DB 32 such as the above recipe browsing history information, recipe posting history information, report posting history information, approval history information, reply history information, etc. Is also stored.
 また、本例のユーザDB32においては、不適フラグFi、及び遅滞傾向フラグFdがユーザIDごとに対応づけられて記憶されているが、これら不適フラグFi、遅滞傾向フラグFdについては後述する。 In addition, in the user DB 32 of this example, the inappropriate flag Fi and the delay tendency flag Fd are stored in association with each user ID. The inappropriate flag Fi and the delay tendency flag Fd will be described later.
 なお、図1において、レシピサイト運営システム3が備える親密情報DB35の記憶情報については後述する。 In addition, in FIG. 1, the memory | storage information of the intimacy information DB35 with which the recipe site management system 3 is provided is mentioned later.
 また、図1において、ネットワーク2の構成は多様な例が想定される。例えば、インターネットを始めとして、イントラネット、エキストラネット、LAN(Local Area Network)、CATV(Community Antenna TeleVision)通信網、仮想専用網(Virtual Private Network)、電話回線網、移動体通信網、衛星通信網等が想定される。
 またネットワーク2の全部又は一部を構成する伝送媒体についても多様な例が想定される。例えばIEEE(Institute of Electrical and Electronics Engineers)1394、USB(Universal Serial Bus)、電力線搬送、電話線等の有線でも、IrDA(Infrared Data Association)のような赤外線、ブルートゥース(登録商標)、802.11無線、携帯電話網、衛星回線、地上波デジタル網等の無線でも利用可能である。
In FIG. 1, various examples of the configuration of the network 2 are assumed. For example, the Internet, intranet, extranet, LAN (Local Area Network), CATV (Community Antenna TeleVision) communication network, virtual private network, telephone line network, mobile communication network, satellite communication network, etc. Is assumed.
Various examples of transmission media constituting all or part of the network 2 are also envisaged. For example, IEEE (Institute of Electrical and Electronics Engineers) 1394, USB (Universal Serial Bus), power line carrier, telephone line etc. wired, infrared such as IrDA (Infrared Data Association), Bluetooth (registered trademark), 802.11 wireless It can also be used by radio such as a mobile phone network, satellite line, and digital terrestrial network.
[1-2.コンピュータ装置のハードウェア構成]

 図3に、図1で示したレシピサイトサーバ31をはじめとした各装置(ユーザDB32、レシピDB33、レポートDB34、親密情報DB35、及びユーザ端末4)を構成するコンピュータ装置のハードウェア構成を示す。
 図3において、コンピュータ装置のCPU(Central Processing Unit)101は、ROM(Read Only Memory)102に記憶されているプログラム、または記憶部108からRAM(Random Access Memory)103にロードされたプログラムに従って各種の処理を実行する。RAM103にはまた、CPU101が各種の処理を実行する上において必要なデータなども適宜記憶される。
 CPU101、ROM102、及びRAM103は、バス104を介して相互に接続されている。このバス104には、入出力インタフェース105も接続されている。
 入出力インタフェース105には、キーボード、マウス、タッチパネルなどよりなる入力部106、LCD(Liquid Crystal Display)、CRT(Cathode Ray Tube)、有機EL(Electroluminescence)パネルなどよりなるディスプレイ(表示装置)、並びにスピーカなどよりなる出力部107、HDD(Hard Disk Drive)やフラッシュメモリ装置などより構成される記憶部108、外部装置との間で相互通信を行うための通信部109が接続されている。
 入出力インタフェース105にはまた、必要に応じてメディアドライブ110が接続され、磁気ディスク、光ディスク、光磁気ディスク、或いは半導体メモリなどのリムーバブルメディア111が適宜装着され、リムーバブルメディア111に対する情報の書込や読出が行われる。
[1-2. Hardware configuration of computer device]

FIG. 3 shows a hardware configuration of a computer device constituting each device (user DB 32, recipe DB 33, report DB 34, intimacy information DB 35, and user terminal 4) including the recipe site server 31 shown in FIG.
In FIG. 3, a CPU (Central Processing Unit) 101 of a computer apparatus performs various processes according to a program stored in a ROM (Read Only Memory) 102 or a program loaded from a storage unit 108 to a RAM (Random Access Memory) 103. Execute the process. The RAM 103 also appropriately stores data necessary for the CPU 101 to execute various processes.
The CPU 101, ROM 102, and RAM 103 are connected to each other via a bus 104. An input / output interface 105 is also connected to the bus 104.
The input / output interface 105 includes an input unit 106 including a keyboard, a mouse, and a touch panel, a display (display device) including an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), an organic EL (Electroluminescence) panel, and a speaker. Are connected to a storage unit 108 composed of an HDD (Hard Disk Drive) or a flash memory device, and a communication unit 109 for mutual communication with an external device.
A media drive 110 is also connected to the input / output interface 105 as necessary, and a removable medium 111 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and information can be written to the removable medium 111. Reading is performed.
 このようなコンピュータ装置では、通信部109による通信によりデータやプログラムのアップロード、ダウンロードが行われたり、リムーバブルメディア111を介したデータやプログラムの受け渡しが可能である。
 CPU101が各種のプログラムに基づいて処理動作を行うことで、特にレシピサイトサーバ31としてのコンピュータ装置においては以降で説明する情報処理や通信が実行される。
In such a computer apparatus, data and programs can be uploaded and downloaded through communication by the communication unit 109, and data and programs can be transferred via the removable medium 111.
When the CPU 101 performs processing operations based on various programs, information processing and communication described below are executed particularly in the computer device as the recipe site server 31.
 なお、レシピサイトサーバ31をはじめとして図1で示した各装置は、図3のようなコンピュータ装置が単一で構成されることに限らず、複数のコンピュータ装置がシステム化されて構成されてもよい。複数のコンピュータ装置は、LAN等によりシステム化されていてもよいし、インターネット等を利用したVPN等により遠隔地に配置されたものでもよい。
1 including the recipe site server 31 is not limited to a single computer device as shown in FIG. 3, and a plurality of computer devices may be configured as a system. Good. The plurality of computer devices may be systemized by a LAN or the like, or may be arranged at a remote place by a VPN using the Internet or the like.
[1-3.第1の実施の形態としての承認制御手法]

 図4の機能ブロック図を参照して、レシピサイトサーバ31が実現する第1の実施の形態としての承認制御に係る各種機能について説明する。
 図示するようにレシピサイトサーバ31は、機能ごとに分けて親密度評価処理部F1、不適レポータ判定処理部F2、及び承認制御処理部F3を有するものとして表すことができる。
[1-3. Approval control method as the first embodiment]

With reference to the functional block diagram of FIG. 4, various functions related to the approval control as the first embodiment realized by the recipe site server 31 will be described.
As shown in the figure, the recipe site server 31 can be expressed as having a closeness evaluation processing unit F1, an inappropriate reporter determination processing unit F2, and an approval control processing unit F3 for each function.
 親密度評価処理部F1は、レシパとレポータとの親密度を、レシパ、レポータそれぞれに紐付く情報に基づいて評価する。
 本例における親密度評価処理部F1は、ユーザDB32に記憶された行動履歴情報に基づいてレシパとレポータとの親密度を評価する。具体的に、親密度評価処理部F1は、レシパによるレポータに対する過去のレポート承認回数に基づいて両者の間の親密度を評価する。例えば、ユーザAがレシパ、ユーザBがユーザAの投稿レシピに対する作成レポートを投稿したレポータであるとすると、ユーザBがユーザAの投稿レシピに対して過去に投稿した作成レポートのうち、ユーザAにより承認された作成レポートの数を上記の「レポート承認回数」として特定する。
The familiarity evaluation processing unit F1 evaluates the familiarity between the receiver and the reporter based on information associated with the receiver and the reporter.
The familiarity evaluation processing unit F1 in this example evaluates the familiarity between the receiver and the reporter based on the action history information stored in the user DB 32. Specifically, the familiarity evaluation processing unit F1 evaluates the familiarity between the two based on the past report approval count for the reporter by the receiver. For example, if user A is a reporter, and user B is a reporter who has posted a creation report for user A's posted recipe, user B can create a report that has been posted by user A in the past. The number of approved created reports is specified as the above “number of report approvals”.
 レシピサイトにおいて、レシパによるレポータに対する過去のレポート承認回数は、両者の間のコミュニケーション頻度を推し量る指標として機能する。このため、上記のレポート承認回数を特定することで、レシパとレポータとの間の親密度を適切に評価することができる。
 ここで、後述するように本実施の形態では、レシパとの間の親密度が一定度以上である「親密レポータ」としてのレポータについては、該レシパへの投稿レポートが自動承認されるようになる。このため、上記のように親密度を適切に評価できるということは、親密の確度が比較的高いレポータを自動承認することができるということを意味する。
In the recipe site, the number of past report approvals for the reporter by the receiver functions as an index for estimating the communication frequency between the two. For this reason, it is possible to appropriately evaluate the intimacy between the receiver and the reporter by specifying the number of report approvals.
Here, as will be described later, in this embodiment, for a reporter as an “intimate reporter” whose intimacy with a receiver is a certain degree or higher, a report posted to the receiver is automatically approved. . For this reason, being able to appropriately evaluate the intimacy as described above means that a reporter with a relatively high degree of intimacy can be automatically approved.
 また、親密度評価処理部F1は、レポータによる投稿レシピに対してレシパが過去に作成レポートを投稿している場合には、該レポータによる投稿レシピに対する該レシパのレポート投稿回数に基づき、親密度を評価する。またこの際、親密度評価処理部F1は、レポータによる投稿レシピに対するレシパの投稿レポートについての承認回数も考慮する。
 具体的に、本例の親密度評価処理部F1は、レポータによる投稿レシピに対してレシパが過去に作成レポートを投稿している場合には、上記した「レポート承認回数」を特定すると共に、レポータによる投稿レシピに対するレシパのレポート投稿回数、及び該レシパの投稿レポートに対してレポータが承認を行った回数を特定する。そして、これら特定した回数の値に基づいて、レシパとレポータとの間の親密度を計算する。本例では、これら特定した回数の値の合計値を親密度として計算する。
In addition, when the reporter has posted a creation report in the past with respect to a posted recipe by the reporter, the closeness evaluation processing unit F1 determines the familiarity based on the number of report submissions of the reporter to the posted recipe by the reporter. evaluate. At this time, the intimacy evaluation processing unit F1 also considers the number of approvals for the reporter posting report for the posting recipe by the reporter.
Specifically, the intimacy evaluation processing unit F1 of this example specifies the above-mentioned “report approval count” and reports the reporter when the reporter has posted a created report in the past with respect to the posting recipe by the reporter. The number of postings of the reporter for the posting recipe by and the number of times the reporter has approved the posting report of the receiver. Then, the closeness between the receiver and the reporter is calculated based on the specified number of times. In this example, the total value of these specified number of times is calculated as the familiarity.
 ここで、レポータによる投稿レシピに対するレシパのレポート投稿回数としても、両者の間のコミュニケーション頻度を推し量る指標として機能する。従って、上記による親密度の評価を行うことで、レシパとレポータ両者間の親密度を適切に評価することができる。さらには、親密の確度が比較的高いレポータを自動承認することができる。 Here, the reporter's report submission count for the posting recipe by the reporter also functions as an index for estimating the communication frequency between the two. Therefore, by evaluating the intimacy as described above, it is possible to appropriately evaluate the intimacy between both the receiver and the reporter. Furthermore, it is possible to automatically approve reporters with relatively high intimacy.
 また、上記のように親密度の評価にあたってレシパの投稿レポートに対するレポータによる承認回数を考慮していることで、レシパとレポータとの間の親密度がより適切に評価され、親密の確度がさらに高いレポータを自動承認することができる。 In addition, as described above, considering the number of approvals by the reporter for the reporter's post report in evaluating the intimacy, the intimacy between the receiver and the reporter is more appropriately evaluated, and the intimacy accuracy is even higher. Reporter can be automatically approved.
 なお、上記した親密度の評価において、「承認」は、少なくともユーザの手動による承認のみを対象とすればよい。或いは、後述する自動承認を対象に含めることもできる。 In the above evaluation of intimacy, “approval” should be at least subject to manual approval by the user. Or the automatic approval mentioned later can also be included in object.
 続いて、不適レポータ判定処理部F2は、レポータが過去に投稿したレポートについての情報信頼度を評価した結果に基づき、レポータが不適レポータであるか否かを判定する。
 ここで、レシピサイトとしては、レシピに対する作成レポートの投稿ごとにレポータに対してポイント等のインセンティブの付与を行う場合があり、その場合には、インセンティブの荒稼ぎ等を目的として、情報信頼性の低い作成レポートを比較的大量に投稿するレポータが出現することがある。この種のレポータについては、その投稿レポートについてレシパに承認を要求することはレシパの承認に係る負担を徒に増大させることに繋がるため望ましくない。このため本実施の形態では、この種のレポータを「不適レポータ」として特定し、後述するように、不適レポータからの投稿レポートが承認要求の対象から除外されるようにする。
Subsequently, the inappropriate reporter determination processing unit F2 determines whether or not the reporter is an inappropriate reporter based on the result of evaluating the information reliability of the report posted by the reporter in the past.
Here, the recipe site may give incentives such as points to the reporter every time a creation report for a recipe is posted. In that case, the information reliability is low for the purpose of earning incentives, etc. Reporters that post a relatively large amount of created reports may appear. For this type of reporter, requesting approval from the receiver for the post report is undesirable because it increases the burden on the approval of the receiver. For this reason, in this embodiment, this type of reporter is specified as an “unsuitable reporter”, and a post report from the unsuitable reporter is excluded from the approval request as described later.
 本例の不適レポータ判定処理部F2は、不適レポータであるか否かを、レポータが同一又は類似画像を用いたレポートを複数のレシピに対して投稿しているか否かに基づき判定する。
 ポイント等の荒稼ぎを目的とした不適レポータにとって、作成レポートの投稿にあたり作成した料理の写真をいちいち撮影することは手間であり、同一画像、又は全体的な明るさや色味を僅かに変更する等の比較的軽微な画像加工を施す等した類似画像を複数のレシピそれぞれへの投稿レポート間で使い回すといった事象が確認されている。具体的には、例えば或る「料理r」についてのレシピとして、レシパAによるレシピa、レシパBによるレシピb、レシパCによるレシピcが投稿されている場合において、それらレシピa、レシピb、レシピcのそれぞれに同一又は類似画像を用いた作成レポートが投稿されるといったケースである。
 この点に鑑み、本例では複数のレシピへの投稿レポートに用いられるそれぞれの画像間の類似性に基づき、不適レポータの判定を行う。
The inappropriate reporter determination processing unit F2 of this example determines whether or not the reporter is an inappropriate reporter based on whether or not the reporter has posted reports using the same or similar images to a plurality of recipes.
For unsuitable reporters for the purpose of rough earning such as points, it is troublesome to take pictures of the dishes created when posting the creation report, such as changing the same image or the overall brightness and color slightly It has been confirmed that similar images, such as those with relatively minor image processing, are reused between submission reports for each of a plurality of recipes. Specifically, for example, when a recipe a by Recipe A, a recipe b by Recipe B, and a recipe c by Recipe C are posted as a recipe for a certain “dish r”, the recipe a, recipe b, recipe In this case, a creation report using the same or similar image is posted to each of c.
In view of this point, in this example, an inappropriate reporter is determined based on the similarity between images used in reports submitted to a plurality of recipes.
 不適レポータ判定処理部F2は、不適レポータの判定にあたり、先ずは対象とするレポータが過去に投稿した作成レポートのうち、投稿先レシピが異なる複数の作成レポートを特定し、それらの作成レポートに用いられている各画像を取得する。そして、取得した各画像について、取得した他の全ての画像との間の類似度をそれぞれ計算し、類似度が一定値以上の関係となっている画像を同一又は類似画像として特定する。この際、対象とするレポータは例えば料理ごとに同一又は類似画像を使い分けることも考えられ、その場合には、同一又は類似画像として複数の組が特定され得る。例えば、取得した画像の総数が「10」であった場合に、そのうち「画像g1、画像g2、画像g3」による組と、「画像g5、画像g6、画像g7」による組とが、それぞれ類似度≧一定値の関係となっている画像として特定される等である。 In determining the inappropriate reporter, the inappropriate reporter determination processing unit F2 first identifies a plurality of generated reports with different posting destination recipes from among the generated reports posted by the target reporter in the past, and is used in those generated reports. Get each image you have. Then, for each acquired image, the degree of similarity between all the other acquired images is calculated, and images having a degree of similarity greater than or equal to a certain value are specified as the same or similar images. At this time, for example, it is conceivable that the target reporter uses the same or similar images for each dish. In this case, a plurality of sets can be specified as the same or similar images. For example, when the total number of acquired images is “10”, the combination of “image g1, image g2, image g3” and the combination of “image g5, image g6, image g7” ≧ Identified as an image having a relationship of a certain value.
 なお、画像間の類似度を評価する手法としては、周知の手法を採用することができる。例えば、比較対象とする各画像から検出したエッジの一致度合いを類似度として計算することができる。或いは、例えば4×4画素サイズによる領域等、画像を構成する各領域ごとに対象とする画像間で画素値の平均値の差を計算し、該差の合計値を類似度として計算するなどの手法も採ることができ、類似度を評価する手法は特定の手法に限定されるものではない。 It should be noted that a known method can be adopted as a method for evaluating the similarity between images. For example, the degree of coincidence of the edges detected from each image to be compared can be calculated as the similarity. Alternatively, for example, an average pixel value difference is calculated between target images for each area constituting the image, such as an area with a 4 × 4 pixel size, and the total value of the differences is calculated as a similarity. A technique can also be adopted, and the technique for evaluating the degree of similarity is not limited to a specific technique.
 不適レポータ判定処理部F2は、特定した同一又は類似画像の数が一定値以上であれば、対象とするレポータが不適レポータであると判定する。これは、対象とするレポータによる投稿レポートの情報信頼性が一定度以下であれば、該レポータを不適レポータと判定していることに相当する。
 ここで、上記のように同一又は類似画像が複数組特定された場合、すなわち同一又は類似画像の数が複数計算された場合には、それらの数のうち最大の数が一定値以上であれば、対象とするレポータが不適レポータであると判定する。
 なお以下、同一又は類似画像については「同一・類似画像」と表記する。
The inappropriate reporter determination processing unit F2 determines that the target reporter is an inappropriate reporter if the number of identified identical or similar images is equal to or greater than a certain value. This corresponds to determining that the reporter is an inappropriate reporter if the information reliability of the posted report by the target reporter is below a certain level.
Here, when a plurality of sets of the same or similar images are specified as described above, that is, when a plurality of the same or similar images are calculated, if the maximum number among them is a certain value or more, , It is determined that the target reporter is an inappropriate reporter.
Hereinafter, the same or similar images are referred to as “same / similar images”.
 不適レポータ判定処理部F2は、不適レポータと判定したレポータについては、該レポータのユーザIDと対応づけられてユーザDB32に記憶された不適フラグFaをOFF(例えば「0」)からON(例えば「1」)に変更する処理を行う。 For the reporter determined to be an inappropriate reporter, the inappropriate reporter determination processing unit F2 sets the inappropriate flag Fa associated with the reporter's user ID and stored in the user DB 32 from OFF (for example, “0”) to ON (for example, “1”). )) Is performed.
 承認制御処理部F3は、親密度評価処理部F1が評価したレシパとレポータとの間の親密度に基づき、レポータが投稿した作成レポートの承認に係る制御を行う。具体的に、承認制御処理部F3は、親密度が一定度以上のレポータである親密レポータがレポートを投稿した場合は、レシパに当該レポートについての承認を要求した後、レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、親密度が一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、レシパに当該レポートについての承認を要求する一方で、時間経過に応じたレポート承認処理を行わない。
 すなわち、承認の要求については、親密レポータによる投稿レポート、及び非親密レポータによる投稿レポートの双方を対象として行われるが、時間経過に応じたレポート承認処理、つまりレシピサイトサーバ31による自動承認は親密レポータによる投稿レポートのみを対象として行われるものである。
The approval control processing unit F3 performs control related to the approval of the created report posted by the reporter based on the closeness between the reporter and the reporter evaluated by the closeness evaluation processing unit F1. Specifically, the approval control processing unit F3, when an intimate reporter that is a reporter with a closeness of a certain degree or more, submits a report, after requesting the reporter to approve the report, manual approval from the receiver Even if not, the report approval process is performed according to the passage of time, and if a non-intimate reporter who is a reporter whose intimacy is not more than a certain degree posts the report, the reporter is requested to approve the report, but the time has passed The report approval process according to is not performed.
In other words, the approval request is performed for both the posting report by the intimate reporter and the posting report by the non-intimate reporter, but the report approval processing according to the passage of time, that is, the automatic approval by the recipe site server 31 is performed. It is performed only for the contribution report by.
 先ず、承認制御処理部F3が行う親密レポータの判定について説明する。
 本例では、レシピに対する作成レポートが投稿されるごとに、親密度評価処理部F1によりレシパとレポータとの間の親密度計算が行われ、承認制御処理部F3は、計算された親密度に基づき、レポータが親密レポータであるか否かを判定する。本例の承認制御処理部F3は、上述のように親密度評価処理部F1がレポータによる投稿レシピに対してレシパが過去に作成レポートを投稿している場合か否かで異なる親密度計算手法を採ることに対応して、それぞれ異なる閾値を用いて親密レポータか否かの判定を行う。具体的に、レポータによる投稿レシピに対してレシパが過去に作成レポートを投稿していない場合に計算された親密度については、親密度が当該場合に対応して設定された閾値(以下「第一親密閾値」と表記)以上であるか否かにより親密レポータか否かを判定し、レポータによる投稿レシピに対してレシパが過去に作成レポートを投稿している場合に計算された親密度については、親密度が当該場合に対応して設定された閾値(以下「第二親密閾値」と表記)以上であるか否かにより親密レポータか否かを判定する。
First, the intimacy reporter determination performed by the approval control processing unit F3 will be described.
In this example, every time a creation report for a recipe is posted, the familiarity evaluation processing unit F1 calculates the familiarity between the receiver and the reporter, and the approval control processing unit F3 is based on the calculated familiarity. Determine whether the reporter is an intimate reporter. As described above, the approval control processing unit F3 of the present example uses different intimacy calculation methods depending on whether or not the reciever evaluation processing unit F1 has posted a creation report in the past for a posting recipe by a reporter. Corresponding to the selection, it is determined whether the reporter is an intimate reporter using different threshold values. Specifically, for the intimacy calculated when the reporter has not posted a creation report in the past for the posting recipe by the reporter, the intimacy is set to a threshold value (hereinafter referred to as “first” It is determined whether or not it is an intimate reporter by whether or not it is greater than or equal to the “intimacy threshold”, and the intimacy calculated when the reporter has posted a creation report in the past for the posting recipe by the reporter, Whether or not the intimacy is an intimacy reporter is determined based on whether or not the intimacy is equal to or higher than a threshold (hereinafter referred to as “second intimacy threshold”) set in correspondence with the case.
 レポータが親密レポータであると判定した場合、承認制御処理部F3は該レポータが親密レポータである旨を表す情報を親密情報DB35に記憶させる。具体的には、レシパのユーザIDに対応づけて、親密レポータと判定したレポータのユーザIDを対応づけて記憶させる。 When it is determined that the reporter is an intimate reporter, the approval control processing unit F3 stores information indicating that the reporter is an intimate reporter in the intimacy information DB 35. Specifically, the user ID of the reporter determined to be an intimate reporter is stored in association with the user ID of the reporter.
 図5は、親密情報DB35の記憶情報を例示した図である。
 上記のような承認制御処理部F3による記憶処理が行われることで、親密情報DB35には、レシパとしてのユーザごとに、該ユーザにとっての親密レポータが何れのユーザであるかを表す情報が構築される。
FIG. 5 is a diagram illustrating information stored in the intimacy information DB 35.
By performing the storage process by the approval control processing unit F3 as described above, in the intimacy information DB 35, information indicating which user is the intimacy reporter for the user is constructed for each user as a receiver. The
 承認制御処理部F3は、上記のような親密レポータの判定結果に基づき、作成レポートの承認についての制御を行う。具体的に承認制御処理部F3は、或るレシパによる投稿レシピに対し該レシパにとっての親密レポータが作成レポートを投稿した場合は、レシパに当該作成レポートについての承認を要求した後、レシパから当該作成レポートについての手動による承認がなくても、時間経過に応じたレポート承認処理を行う。
 また、或るレシパによる投稿レシピに対し該レシパにとって親密レポータでない非親密レポータが作成レポートを投稿した場合は、レシパに当該作成レポートについての承認を要求する一方で、当該作成レポートにつての時間経過に応じたレポート承認処理を行わない。
The approval control processing unit F3 controls the approval of the created report based on the determination result of the intimate reporter as described above. Specifically, when an intimate reporter for a receiver submits a creation report to a recipe submitted by a certain receiver, the approval control processing unit F3 requests the receiver to approve the creation report, and then creates the creation from the receiver. Even if the report is not manually approved, the report approval process is performed according to the passage of time.
In addition, when a non-intimate reporter who is not an intimate reporter for a recipe for a recipe submitted by a certain receiver submits a creation report, the request for approval of the creation report is requested from the receiver, while the time elapsed for the creation report. The report approval process according to is not performed.
 図6を参照し、作成レポートについての承認要求について説明する。
 本例の場合、承認要求は、対象とするレシパに対して電子メールを送信することで行われる。以下、このように承認を要求する電子メールのことを「承認要求メール」と表記する。
 本例では、作成レポートについての承認要求は、対象とするレシパの投稿レシピに対する投稿レポートとして複数の未承認レポートがある場合は、それら複数の未承認レポートについての承認をまとめて要求する形式で行う。
 図6では、このように複数の未承認レポートについての承認をまとめて要求する形式による承認要求メールの例を示している。
With reference to FIG. 6, the approval request for the created report will be described.
In the case of this example, the approval request is made by sending an e-mail to the target receiver. Hereinafter, an e-mail requesting approval in this way is referred to as an “approval request mail”.
In this example, if there are multiple unapproved reports as post reports for the recipe recipe of the target receiver, the approval request for the created report is made in a format that requests approval for the multiple unapproved reports at once. .
FIG. 6 shows an example of an approval request mail in a format that requests approval for a plurality of unapproved reports in this way.
 この場合の承認要求メールにおいては、未承認レポートについての承認を要求するメッセージが提示されると共に、承認を要求する未承認レポートを特定するための情報、具体的に図6の例では未承認レポートの投稿内容を表す画像やテキストの情報がそれぞれ提示される。 In the approval request mail in this case, a message requesting approval for the unapproved report is presented, and information for specifying the unapproved report requesting approval, specifically the unapproved report in the example of FIG. Image and text information representing the content of the post will be presented.
 さらに、本例における承認要求メールには、個々の未承認レポートに対する承認指示操作を可能とするための承認チェックボックスCb1が未承認レポートごとに設けられている。ユーザは、未承認レポートについて承認を行う場合は、該当する未承認レポートに対して設けられた承認チェックボックスcb1にチェックを入れ、承認要求メールに設けられた送信ボタンB1を操作する。これにより、チェックの入れられた未承認レポートについての承認を指示する情報がレシピサイトサーバ31に返信され、レシピサイトサーバ31(承認制御処理部F3)は該情報に基づいて該当する未承認レポートについての承認処理を行う。 Furthermore, in the approval request mail in this example, an approval check box Cb1 is provided for each unapproved report for enabling an approval instruction operation for each unapproved report. When the user approves an unapproved report, the user checks the approval check box cb1 provided for the corresponding unapproved report, and operates the send button B1 provided in the approval request mail. Thereby, information instructing approval for the checked unapproved report is returned to the recipe site server 31, and the recipe site server 31 (approval control processing unit F <b> 3) determines the corresponding unapproved report based on the information. Perform the approval process.
 このように本例では、レシパに対する承認の要求として、個々の未承認レポートに対する承認指示操作が可能な形式による要求を行っている。これにより、レシパによるレポート承認の容易性が増し、レポート掲載数低下の抑制効果を高めることができる。また、レシパと非親密レポータとの間のコミュニケーション促進を図ることができる。 In this way, in this example, as a request for approval to the receiver, a request is made in a format that allows an approval instruction operation for each unapproved report. Thereby, the ease of report approval by the receiver increases, and the effect of suppressing the reduction in the number of report publications can be enhanced. Further, communication between the receiver and the non-intimate reporter can be promoted.
 また、この場合の承認要求メールには、未承認レポートを投稿したレポータの親密レポータへの登録指示操作を可能とするための登録チェックボックスcb2が設けられている。なお、登録チェックボックスcb2は、承認が要求される作成レポートの投稿レポータに非親密レポータが含まれている場合にのみ、承認要求メールに設けられるものである。該当する非親密レポータが複数存在する場合、登録チェックボックスcb2はそれら非親密レポータごとに設けられる。
 ユーザは、親密レポータへの登録を行う場合は、該当する登録チェックボックスcb2にチェックを入れ、承認要求メールに設けられた送信ボタンB1を操作する。これにより、チェックの入れられたレポータを親密レポータに登録指示する情報がレシピサイトサーバ31に返信され、レシピサイトサーバ31は該情報に基づいて該当するレポータを親密レポータとして登録する処理を行う。具体的には、親密情報DB35を対象とした情報記憶処理として、該当するレシパのユーザIDに対して登録対象とされたレポータのユーザIDを対応づけて記憶させる処理を行う。
The approval request mail in this case is provided with a registration check box cb2 for enabling a registration instruction operation to the intimate reporter of the reporter who posted the unapproved report. The registration check box cb2 is provided in the approval request mail only when the posting reporter of the created report that requires approval includes a non-intimate reporter. When there are a plurality of corresponding non-intimate reporters, the registration check box cb2 is provided for each of the non-intimate reporters.
When registering in the intimate reporter, the user checks the corresponding registration check box cb2 and operates the send button B1 provided in the approval request mail. As a result, information for instructing registration of the checked reporter to the intimate reporter is returned to the recipe site server 31, and the recipe site server 31 performs processing for registering the corresponding reporter as the intimate reporter based on the information. Specifically, as information storage processing for the intimate information DB 35, processing is performed in which the user ID of the reporter that is the registration target is associated with the user ID of the corresponding receiver and stored.
 上記のようにレシパに対する承認の要求としてレポータの親密レポータへの登録指示操作が可能な形式による要求を行うことで、レシパは非親密レポータを手動により親密レポータに登録することが可能とされる。
 十分な親密性を感じるか否かはレシパ個人の性格やレポータとのコミュニケーション内容等の条件で異なり得るものであり、コミュニケーションが僅かであっても十分な親密性が築かれるケースも想定され得る。このため、親密レポータの登録として、親密度に基づく自動登録のみでなく手動登録が可能とされることで、自動承認の対象者数の増加が見込まれる。従って、ユーザのレポート承認に係る手間の抑制効果を高めることができる。
 また、承認要求において親密レポータへの登録指示操作を可能としている点で、親密レポータの登録を促すための情報を承認要求とは別途にユーザに送信する必要がなくなり、レシピサイトサーバ31の処理負担軽減を図ることができる。
As described above, by making a request in a format that allows the reporter to instruct to register with the intimate reporter as an approval request to the reporter, the receiver can manually register the non-intimate reporter with the intimate reporter.
Whether or not sufficient feeling of intimacy is felt may differ depending on the personality of the receiver and the contents of communication with the reporter, and there may be a case where sufficient intimacy is established even if there is little communication. For this reason, as the registration of the intimate reporter, not only automatic registration based on closeness but also manual registration is possible, so that the number of persons subject to automatic approval is expected to increase. Therefore, it is possible to increase the effect of suppressing the trouble related to the user's report approval.
In addition, since the registration request operation to the intimate reporter is enabled in the approval request, it is not necessary to send information for prompting the registration of the intimate reporter to the user separately from the approval request, and the processing load of the recipe site server 31 is eliminated. Mitigation can be achieved.
 上述のように承認制御処理部F3は、親密レポータが投稿した作成レポートについては、承認要求を行った後、時間経過に応じて自動的に承認処理を行う。本例の承認制御処理部F3は、当該作成レポートについての承認処理については、当該作成レポートの承認要求を行った日時からの経過時間が一定時間以上となったことに応じて実行する。 As described above, the approval control processing unit F3 automatically performs an approval process with the passage of time after making an approval request for the created report posted by the intimate reporter. The approval control processing unit F3 of this example executes the approval process for the created report according to the fact that the elapsed time from the date when the approval request for the created report is made has become a certain time or more.
 なお、本例の承認制御処理部F3は、上記のような自動的な承認処理、及びレシパの操作に基づく承認処理として、作成レポートごとに用意された承認フラグFaをOFF(例えば「0」)からON(例えば「1」)に変更する処理を行う。
 承認フラグFaは、本例ではレポートDB34においてレポートIDごとに対応づけられて記憶された情報とされている。
Note that the approval control processing unit F3 of this example turns off the approval flag Fa prepared for each created report as an automatic approval process as described above and an approval process based on the operation of the receiver (for example, “0”). To change from ON to ON (for example, “1”).
In this example, the approval flag Fa is information stored in the report DB 34 in association with each report ID.
 ここで、承認制御処理部F3は、未承認のレポートについてレシパに承認を要求する前に、当該レポートが不適レポータにより投稿されたレポートである不適レポートか否かを判定する。そして、不適レポートであると判定した場合は、当該レポートについての承認を要求しない。本例では、上述した不適レポータ判定処理部F2の処理により、不適レポータとしてのユーザがユーザDB32に記憶された不適フラグFiのON/OFFにより管理される。承認制御処理部F3は、対象とするレポートを投稿したユーザに対応づけられている不適フラグFiがONであれば、当該レポートを不適レポートと判定し、当該レポートについては承認要求の対象から除外する。 Here, the approval control processing unit F3 determines whether or not an unapproved report is an inappropriate report that is a report posted by an inappropriate reporter before requesting approval from the receiver. If it is determined that the report is inappropriate, the report is not requested for approval. In this example, the user as an inappropriate reporter is managed by ON / OFF of the inappropriate flag Fi stored in the user DB 32 by the process of the inappropriate reporter determination processing unit F2 described above. If the inappropriate flag Fi associated with the user who posted the target report is ON, the approval control processing unit F3 determines that the report is an inappropriate report and excludes the report from the approval request. .
 これにより、未承認レポートのうちシステム側で事前に不適と判定されたレポータの作成レポートについては、レシパに承認が要求されない。このため、当該レポートについてレシパによる承認の手間が省かれ、従って、レシパのレポート承認に係る負担抑制効果を高めることができる。 ∙ As a result, reporter creation reports that are determined to be inappropriate by the system in advance are not required to be approved by the receiver. For this reason, the trouble of approval by the receiver for the report is saved, and therefore, the burden suppressing effect related to the report approval of the receiver can be enhanced.
 また、承認制御処理部F3は、レシパの過去におけるレポート承認行動を分析した結果に基づき、承認を要求するタイミングを調整する。
 具体的に、本例では、上記のレポート承認行動の分析として、レシパの過去の承認済みレポートについて承認要求から承認を行うまでに要した時間を分析する。具体的には、レシパの過去の承認済みレポートについて、承認要求から承認を行うまでに要した時間の平均値を計算し、該平均値の大きさに応じて承認を要求するタイミングを調整する。
 本例では、該平均値が大きいほど(つまり承認が滞りがちであるほど)、承認を要求するタイミングが早められるように承認の要求タイミングを調整する。
Further, the approval control processing unit F3 adjusts the timing of requesting approval based on the result of analyzing the report approval behavior of the receiver in the past.
Specifically, in this example, as the analysis of the above report approval behavior, the time required from the approval request to the approval of the past approved report of the receiver is analyzed. Specifically, for the past approved report of the receiver, the average value of the time required from the approval request to the approval is calculated, and the timing for requesting the approval is adjusted according to the size of the average value.
In this example, the approval request timing is adjusted so that the approval request timing is advanced as the average value increases (that is, the approval tends to be delayed).
 承認を要求するタイミングの調整手法として、例えば以下の手法を採る。
 先ず前提として、本例では、1つの投稿レシピごとに、以下の(条件1)又は(条件2)を満たすことに応じて該投稿レシピに対する未承認レポートについての承認要求を行う。
 (条件1)未承認レポート数が所定の閾値(以下「数閾値th」と表記)以上。
 (条件2)最古の未承認レポートの投稿日時からの経過時間が所定の閾値(以下「時間閾値TH」と表記)以上。
 この前提において、上記した平均値が大きいほど、数閾値th、及び時間閾値THとして小さな値を用いる。
For example, the following method is adopted as a method for adjusting the timing for requesting approval.
First, as a premise, in this example, an approval request for an unapproved report for the posted recipe is made for each posted recipe in accordance with the following (Condition 1) or (Condition 2).
(Condition 1) The number of unapproved reports is equal to or greater than a predetermined threshold (hereinafter referred to as “number threshold th”).
(Condition 2) The elapsed time from the posting date of the oldest unapproved report is equal to or longer than a predetermined threshold (hereinafter referred to as “time threshold TH”).
Under this premise, the smaller the average value, the smaller the number threshold th and the time threshold TH.
 本例では、承認要求のタイミングは2段階に調整する。具体的に、承認制御処理部F3は、上記の平均値が所定値以上であるレシパを「遅滞傾向ユーザ」と判定し、ユーザDB32においてユーザIDごとに対応づけられて記憶された遅滞傾向フラグFiのうち、当該レシパのユーザIDに対応づけられている遅滞傾向フラグFiをOFF(例えば「0」)からON(例えば「1」)に変更する。
 承認制御処理部F3は、対象とするレシパが遅滞傾向フラグFi=ONである遅滞傾向ユーザである場合は、遅滞傾向フラグFi=OFFである非遅滞傾向ユーザである場合よりも、上記の数閾値th、及び時間閾値THとしてより値の小さい閾値を用いる。これにより、承認が滞りがちなレシパについては、承認を要求するタイミングが通常よりも早められるようになる。
In this example, the approval request timing is adjusted in two stages. Specifically, the approval control processing unit F3 determines a receiver whose average value is equal to or greater than a predetermined value as a “lagging tendency user”, and the lagging tendency flag Fi stored in association with each user ID in the user DB 32. Among them, the delay tendency flag Fi associated with the user ID of the receiver is changed from OFF (for example, “0”) to ON (for example, “1”).
The approval control processing unit F3, when the target receiver is a delayed tendency user with a delayed tendency flag Fi = ON, is more than the above-mentioned number threshold than when it is a non-delayed tendency user with a delayed tendency flag Fi = OFF. A threshold having a smaller value is used as th and the time threshold TH. As a result, the timing for requesting approval for a receiver whose approval tends to be delayed is earlier than usual.
 ここで、上記のように承認制御処理部F3は、レシパとの間の親密度が一定度以上の親密レポータによる投稿レポートを自動承認の対象としている。この場合において、親密度評価処理部F1が前述のように「レシパによるレポータの過去のレポート承認回数」に基づいて親密度を評価することによると、投稿レポートが自動承認されなかったレポータは、レシパへのレポート投稿を繰り返すうちに、その投稿レポートが自動承認されるように図られる。換言すれば、レシパは、同一レポータに対してレポート承認を繰り返すうち該レポータに対するレポート承認を行う手間が省かれるようになるものであり、この点においてレシパの承認に係る負担抑制が図られる。
Here, as described above, the approval control processing unit F3 automatically sets a posting report by an intimate reporter having a closeness with a receiver as a certain degree or more. In this case, when the closeness evaluation processing unit F1 evaluates the closeness based on the “number of reporter past report approvals by the reporter” as described above, the reporter whose post report is not automatically approved is While posting a report to, the posting report is automatically approved. In other words, the reporter can save the trouble of performing report approval for the reporter while repeating report approval for the same reporter, and in this respect, the burden on the approval of the reporter can be reduced.
[1-4.処理手順]

 図7乃至図11のフローチャートを参照して、上記した第1の実施の形態としての手法を実現するために実行すべき処理の手順を説明する。なお、図7乃至図11に示す処理は、レシピサイトサーバ31におけるCPU101が例えばレシピサイトサーバ31におけるROM102や記憶部108等の所定の記憶装置に記憶されたプログラムに基づき実行するものである。
[1-4. Processing procedure]

With reference to the flowcharts of FIGS. 7 to 11, the procedure of processing to be executed to realize the technique as the first embodiment will be described. 7 to 11 is executed by the CPU 101 in the recipe site server 31 based on a program stored in a predetermined storage device such as the ROM 102 or the storage unit 108 in the recipe site server 31, for example.
 図7は、親密レポータの判定に係る処理を示している。
 図7において、レシピサイトサーバ31はステップS101で、作成レポートが投稿されるまで待機し、作成レポートが投稿された場合は、ステップS102でレポータ及び対象レシピのレシパを特定する。すなわち、投稿されたレポートのレポータとしてのユーザ、及び該レポートが対象とするレシピ、換言すれば該レポートの投稿先としてのレシピを投稿したレシパとしてのユーザのそれぞれについて、ユーザIDを特定する。
FIG. 7 shows processing related to determination of an intimate reporter.
In FIG. 7, the recipe site server 31 waits until a creation report is posted in step S101. If the creation report is posted, the reporter and the recipe of the target recipe are specified in step S102. That is, the user ID is specified for each of a user as a reporter of a posted report and a recipe targeted by the report, in other words, a user as a reciper who has posted a recipe as a posting destination of the report.
 ステップS102に続くステップS103でレシピサイトサーバ31は、レシパによるレポータへのレポート承認回数を特定する。すなわち、ユーザDB32に記憶されている前述した承認履歴情報に基づき、レシパによるレポータへの過去におけるレポート承認回数を特定する。 In step S103 following step S102, the recipe site server 31 specifies the number of report approvals to the reporter by the receiver. That is, based on the above-described approval history information stored in the user DB 32, the number of report approvals to the reporter in the past by the receiver is specified.
 ステップS103に続くステップS104でレシピサイトサーバ31は、レシパが過去にレポータの投稿レシピに対してレポート投稿しているか否かを判定する。該判定は、ユーザDB32に記憶されている前述したレポート投稿履歴情報、及びレシピ投稿履歴情報に基づき行うことができる。 In step S104 following step S103, the recipe site server 31 determines whether or not the recipe has been posted to the reporter's posted recipe in the past. This determination can be made based on the aforementioned report posting history information and recipe posting history information stored in the user DB 32.
 ステップS104において、レシパが過去にレポータの投稿レシピに対してレポート投稿していなければ、レシピサイトサーバ31はステップS105に進み、特定した回数情報に基づきレシパとレポータとの間の親密度を計算する。本例では、ステップS103で特定したレポート承認回数を該親密度として扱う。このため、ステップS105の計算処理は不要とすることができる。
 そして、ステップS105に続くステップS106でレシピサイトサーバ31は、親密度が前述した第一親密閾値以上であるか否かを判定し、親密度が第一親密閾値以上であれば、ステップS111に進んで親密レポータ登録処理を行う。すなわち、ステップS102で特定したレポータとレシパとについて、該レポータのユーザIDを該レシパのユーザIDに対応づけて親密情報DB35に記憶させる処理を行う。
 また、ステップS106で親密度が第一親密閾値以上でないと判定した場合、レシピサイトサーバ31はステップS111の処理をパスして図7に示す処理を終える。
In step S104, if the reporter has not posted a report to the reporter's posted recipe in the past, the recipe site server 31 proceeds to step S105, and calculates the closeness between the receiver and the reporter based on the specified number of times information. . In this example, the report approval count specified in step S103 is handled as the familiarity. For this reason, the calculation process of step S105 can be made unnecessary.
In step S106 following step S105, the recipe site server 31 determines whether or not the familiarity is greater than or equal to the first intimacy threshold described above. If the familiarity is greater than or equal to the first intimacy threshold, the process proceeds to step S111. In close reporter registration process. That is, for the reporter and the reporter identified in step S102, a process of storing the reporter user ID in the intimacy information DB 35 in association with the reporter user ID is performed.
If it is determined in step S106 that the familiarity is not equal to or greater than the first intimacy threshold, the recipe site server 31 passes the process of step S111 and ends the process shown in FIG.
 一方、ステップS104において、レシパが過去にレポータの投稿レシピに対してレポート投稿していると判定した場合、レシピサイトサーバ31はステップS107に進み、レポータによる投稿レシピに対するレシパのレポート投稿回数を特定する。該レポート投稿回数は、ユーザDB32に記憶されているレポート投稿履歴情報、及びレシピ投稿履歴情報に基づき特定することができる。 On the other hand, if it is determined in step S104 that the reporter has posted a report for the reporter's posted recipe in the past, the recipe site server 31 proceeds to step S107 and specifies the reporter's report posting count for the posted recipe by the reporter. . The number of report postings can be specified based on report posting history information and recipe posting history information stored in the user DB 32.
 ステップS107に続くステップS108でレシピサイトサーバ31は、レポータによるレシパへのレポート承認回数を特定する。すなわち、レポータによる投稿レシピに対するレシパの投稿レポートのうち、レポータにより承認された投稿レポートの数を特定する。 In step S108 following step S107, the recipe site server 31 specifies the number of report approvals to the receiver by the reporter. That is, the number of posting reports approved by the reporter among the posting reports of the recipe for the posting recipe by the reporter is specified.
 ステップS108に続くステップS109でレシピサイトサーバ31は、特定した回数情報、すなわちステップS103、S107、及びS108で特定した回数情報に基づき、レシパとレポータとの間の親密度を計算する。具体的に、本例ではそれら特定した回数の値の合計値を該親密度として計算する。 In step S109 following step S108, the recipe site server 31 calculates the intimacy between the receiver and the reporter based on the specified number of times information, that is, the number of times information specified in steps S103, S107, and S108. Specifically, in this example, the total value of the specified number of times is calculated as the familiarity.
 ステップS109に続くステップS110でレシピサイトサーバ31は、親密度が前述した第二親密閾値以上であるか否かを判定し、親密度が第二親密閾値以上であれば、ステップS111に進んで親密レポータ登録処理を行う。
 ステップS111の処理を実行したことに応じ、レシピサイトサーバ31は図7に示す処理を終える。
In step S110 following step S109, the recipe site server 31 determines whether or not the intimacy is equal to or greater than the second intimacy threshold described above. If the intimacy is equal to or greater than the second intimacy threshold, the process proceeds to step S111. Perform reporter registration processing.
In response to the execution of the process of step S111, the recipe site server 31 ends the process shown in FIG.
 一方、ステップS110において親密度が第二親密閾値以上でなければ、レシピサイトサーバ31はステップS111の処理をパスして図7に示す処理を終える。 On the other hand, if the closeness is not greater than or equal to the second closeness threshold value in step S110, the recipe site server 31 passes the process in step S111 and ends the process shown in FIG.
 なお、ステップS109の計算処理について、親密度の計算手法は上記の手法に限定されるものではない。
 例えば、ステップS107で特定したレポート投稿回数に対し、ステップS108で特定した承認回数に応じた数値を加算又は乗算した値を求め、該値を、ステップS103で特定したレポート承認回数に対して加算した値を親密度として求める等、親密度の計算手法は多様に考えられるものである。
Note that, in the calculation process of step S109, the calculation method of the familiarity is not limited to the above method.
For example, a value obtained by adding or multiplying a numerical value corresponding to the number of approvals specified in step S108 to the number of report postings specified in step S107 is obtained, and the value is added to the number of report approvals specified in step S103. There are various methods for calculating intimacy, such as obtaining a value as intimacy.
 図8は、不適レポータの判定に係る処理を示している。
 本例では、不適レポータの判定に係る処理は、レポートDB34における記憶情報に基づき、例えばバッチ処理により時間軸上で繰り返し行われる。
 先ず、ステップS201でレシピサイトサーバ31は、ユーザ識別値uを開始値uSにセットする。ユーザ識別値uは、処理対象とするユーザを識別するための識別値であり、開始値uSは、後述する終了値uEと共に、処理対象とするユーザの範囲(ユーザ数)を特定する値として設定されるものである。
FIG. 8 shows processing related to determination of an inappropriate reporter.
In this example, the process related to the determination of the inappropriate reporter is repeatedly performed on the time axis by, for example, batch processing based on the storage information in the report DB 34.
First, in step S201, the recipe site server 31 sets the user identification value u to the start value uS. The user identification value u is an identification value for identifying a user to be processed, and the start value uS is set as a value for specifying a range (number of users) of users to be processed together with an end value uE to be described later. It is what is done.
 ステップS201に続くステップS202でレシピサイトサーバ31は、u番目ユーザによる作成レポート投稿回数がn以上(nは2以上の自然数)であるか否かを判定する。u番目ユーザによる作成レポート投稿回数がn以上でない場合、レシピサイトサーバ31は後述するステップS209に処理を進める。すなわち、本例では不適レポータの判定を画像間の類似度に基づき行うため、判定にあたり必要とされる複数の画像を取得不能であることが予測される場合は、以下で説明する不適レポータ判定に関する処理(S203乃至S208)がパスされるものである。 In step S202 following step S201, the recipe site server 31 determines whether or not the number of creation report postings by the u-th user is n or more (n is a natural number of 2 or more). If the number of creation report postings by the u-th user is not n or more, the recipe site server 31 advances the process to step S209 described later. That is, in this example, the inappropriate reporter is determined based on the similarity between the images. Therefore, when it is predicted that a plurality of images required for the determination cannot be acquired, the inappropriate reporter determination described below is performed. The processing (S203 to S208) is passed.
 ステップS202において、u番目ユーザによる作成レポート投稿回数がn以上であった場合、レシピサイトサーバ31はステップS203に進み、投稿先レシピが異なる作成レポートがあるか否かを判定し、投稿先レシピが異なる作成レポートがなかった場合は、ステップS209に処理を進める。 In step S202, when the number of creation report postings by the u-th user is n or more, the recipe site server 31 proceeds to step S203, determines whether there is a creation report with a different posting destination recipe, and the posting destination recipe is If there is no different creation report, the process proceeds to step S209.
 一方、ステップS203において投稿先レシピが異なる作成レポートがあると判定した場合、レシピサイトサーバ31はステップS204で各作成レポートの投稿画像を取得する。すなわち、投稿先レシピが異なる作成レポートとしての各作成レポートの投稿画像を取得する。 On the other hand, if it is determined in step S203 that there is a creation report with a different posting destination recipe, the recipe site server 31 acquires a posted image of each creation report in step S204. That is, the posting image of each creation report as a creation report with a different posting destination recipe is acquired.
 ステップS204に続くステップS205でレシピサイトサーバ31は、画像間の類似度を評価する。すなわち、前述したように本例では、取得した各画像について、取得した他の全ての画像との間の類似度をそれぞれ計算する。 In step S205 following step S204, the recipe site server 31 evaluates the similarity between images. That is, as described above, in this example, the degree of similarity between each acquired image and all other acquired images is calculated.
 ステップS205に続くステップS206でレシピサイトサーバ31は、同一・類似画像があるか否かを判定する。前述のように本例では、類似度が一定値以上の関係となっている画像を同一・類似画像として特定する。
 同一・類似画像がなければ、レシピサイトサーバ31はステップS209に処理を進める。つまりこの場合、u番目のユーザは不適レポータと判定されない。
In step S206 following step S205, the recipe site server 31 determines whether there is an identical / similar image. As described above, in this example, images having a relationship of similarity of a certain value or more are specified as the same / similar images.
If there is no identical / similar image, the recipe site server 31 advances the process to step S209. That is, in this case, the u-th user is not determined as an inappropriate reporter.
 一方、同一・類似画像があれば、レシピサイトサーバ31はステップS207に進み、同一・類似画像の数がm以上(mは2以上の自然数)であるか否かを判定する。ここで、前述のように、同一・類似画像としては複数の組が特定され得るものであり、同一・類似画像として複数の組が特定された場合、すなわち同一・類似画像の数が複数計算された場合、ステップS207ではそれらの数のうち最大の数がm以上であるか否かを判定する。
 同一・類似画像の数がm以上でなければ、レシピサイトサーバ31はステップS209に処理を進める。
On the other hand, if there is an identical / similar image, the recipe site server 31 proceeds to step S207 and determines whether the number of identical / similar images is m or more (m is a natural number of 2 or more). Here, as described above, a plurality of sets can be specified as the same / similar images, and when a plurality of sets are specified as the same / similar images, that is, a plurality of the same / similar images are calculated. In step S207, it is determined whether or not the maximum number is m or more.
If the number of identical / similar images is not greater than or equal to m, the recipe site server 31 advances the process to step S209.
 同一・類似画像の数がm以上であれば、レシピサイトサーバ31はステップS208に進み、u番目ユーザについての不適設定処理を行う。すなわち、u番目ユーザのユーザIDと対応づけられてユーザDB32に記憶されている不適フラグFaをONとする処理を行う。 If the number of identical / similar images is greater than or equal to m, the recipe site server 31 proceeds to step S208 and performs improper setting processing for the u-th user. That is, a process of turning on the inappropriate flag Fa associated with the user ID of the u-th user and stored in the user DB 32 is performed.
 ステップS208に続くステップS209でレシピサイトサーバ31は、ユーザ識別値uが終了値uE以上であるか否かを判定する。これは、上述した開始値uSと終了値uEとで設定された処理対象範囲内の全ユーザについて、対象処理(ステップS202乃至S208の処理)を完了したか否かを判定していることに相当する。
 ユーザ識別値uが終了値uE以上でなければ、レシピサイトサーバ31はステップS210に進んでユーザ識別値uを1インクリメントした上で、上述したステップS202に戻る。
 一方、ユーザ識別値uが終了値uE以上であれば、レシピサイトサーバ31は図8に示す処理を終える。
In step S209 following step S208, the recipe site server 31 determines whether or not the user identification value u is greater than or equal to the end value uE. This is equivalent to determining whether or not the target processing (the processing of steps S202 to S208) has been completed for all users within the processing target range set by the start value uS and the end value uE described above. To do.
If the user identification value u is not equal to or greater than the end value uE, the recipe site server 31 proceeds to step S210, increments the user identification value u by 1, and then returns to step S202 described above.
On the other hand, if the user identification value u is equal to or greater than the end value uE, the recipe site server 31 ends the process shown in FIG.
 なお、図8に示した処理は、既に不適レポータとして判定済みのユーザを処理対象から除外して行うこともできる。 Note that the process shown in FIG. 8 can be performed by excluding a user who has already been determined as an inappropriate reporter from the processing target.
 図9は、遅滞傾向ユーザの判定に係る処理を示している。
 本例において、遅滞傾向ユーザの判定に係る処理は、前述した承認履歴情報に基づき、例えばバッチ処理により時間軸上で繰り返し行われる。
 図9において、レシピサイトサーバ31は、ステップS301でユーザ識別値uを開始値uSにセットした上で、ステップS302においてu番目ユーザのレポート承認回数が複数回であるか否かを判定する。u番目ユーザのレポート承認回数が複数回でなければ、レシピサイトサーバ31は後述するステップS308に処理を進める。前述のように、本例ではレシパによる投稿レポートの承認に関して、レポート投稿から承認までに要した時間の平均値に基づき遅滞傾向ユーザの判定を行うため、レポート承認回数が複数回でなければ、以下で説明する遅滞傾向ユーザの判定のための処理(S303乃至S307)は行わない。
FIG. 9 shows processing related to determination of a user who tends to be late.
In this example, the processing related to the determination of the user who tends to be delayed is repeatedly performed on the time axis by, for example, batch processing based on the above-described approval history information.
In FIG. 9, the recipe site server 31 sets the user identification value u to the start value uS in step S <b> 301, and then determines in step S <b> 302 whether the number of report approvals for the u-th user is multiple. If the report approval frequency of the u-th user is not a plurality of times, the recipe site server 31 advances the processing to step S308 described later. As mentioned above, in this example, regarding the approval of the posted report by the receiver, the user who is lagging is judged based on the average value of the time from report posting to approval. The process (S303 to S307) for determining a user having a tendency to delay, which will be described in the above, is not performed.
 一方、u番目ユーザのレポート承認回数が複数回であれば、レシピサイトサーバ31はステップS303に進み、各承認済レポートについて、投稿から承認までに要した時間を計算する。すなわち、承認履歴情報に基づき特定されるu番目ユーザの各承認済レポートについて、レポート投稿から承認までに要した時間を計算する。承認済レポートのレポート投稿日時の情報は、該承認済レポートのレポートIDと前述したレポート投稿履歴情報とに基づき特定することができる。 On the other hand, if the report approval frequency of the u-th user is plural, the recipe site server 31 proceeds to step S303, and calculates the time required from posting to approval for each approved report. That is, for each approved report of the u-th user specified based on the approval history information, the time required from report posting to approval is calculated. The report posting date / time information of the approved report can be specified based on the report ID of the approved report and the report posting history information described above.
 ステップS303に続くステップS304でレシピサイトサーバ31は、計算した時間の平均値を計算し、ステップS305で該平均値が所定値以上であるか否かを判定する。
 該平均値が所定値以上であれば、レシピサイトサーバ31はステップS306でu番目ユーザの遅滞傾向フラグFdをONとする処理を実行してステップS308に進み、該平均値が所定値以上でなければ、レシピサイトサーバ31はステップS307でu番目ユーザの遅滞傾向フラグFdをOFFとする処理を実行しステップS308に進む。
In step S304 following step S303, the recipe site server 31 calculates an average value of the calculated times, and determines in step S305 whether the average value is equal to or greater than a predetermined value.
If the average value is equal to or greater than the predetermined value, the recipe site server 31 executes processing for turning on the delay tendency flag Fd of the u-th user in step S306 and proceeds to step S308, and the average value must be equal to or greater than the predetermined value. For example, the recipe site server 31 executes a process of turning off the delay tendency flag Fd of the u-th user in step S307, and proceeds to step S308.
 ステップS308でレシピサイトサーバ31は、ユーザ識別値uが終了値uE以上であるか否かを判定し、ユーザ識別値uが終了値uE以上でなければ、ステップS309に進んでユーザ識別値uを1インクリメントした上でステップS302に戻る。
 一方、ユーザ識別値uが終了値uE以上であれば、レシピサイトサーバ31は図9に示す処理を終える。
In step S308, the recipe site server 31 determines whether or not the user identification value u is equal to or greater than the end value uE. If the user identification value u is not equal to or greater than the end value uE, the process proceeds to step S309 and the user identification value u is set. After incrementing by 1, the process returns to step S302.
On the other hand, if the user identification value u is equal to or greater than the end value uE, the recipe site server 31 ends the process shown in FIG.
 図10は、承認要求に係る処理を示している。
 本例では、図10に示す処理としても、例えばバッチ処理により時間軸上で繰り返し行われる。
 図10において、レシピサイトサーバ31はステップS401で、処理対象レシパを特定する。すなわち、前述したレシピ投稿履歴情報から特定されるレシパのうちから処理対象とする一人のレシパを特定する。
 ステップS401に続くステップS402でレシピサイトサーバ31は、未承認レポートがあるか否かを判定する。すなわち、ステップS401で特定したレシパによる投稿レシピに対する投稿レポートに、未承認レポートがあるか否かを判定する。該判定は、レポート投稿履歴情報と承認履歴情報とに基づき行うことができる。
FIG. 10 shows processing related to the approval request.
In this example, the processing shown in FIG. 10 is also repeatedly performed on the time axis by, for example, batch processing.
In FIG. 10, the recipe site server 31 specifies a processing target receiver in step S401. That is, one receiver to be processed is specified from the receivers specified from the recipe posting history information described above.
In step S402 following step S401, the recipe site server 31 determines whether there is an unapproved report. That is, it is determined whether or not there is an unapproved report in the posted report for the posted recipe by the recipe specified in step S401. This determination can be made based on the report posting history information and the approval history information.
 ステップS402において未承認レポートがないと判定した場合、レシピサイトサーバ31は図10に示す処理を終える。つまり、この場合はレシパに対して承認を要求すべきレポートは存在しないため、以下で説明する承認要求に係る処理(S404乃至S412)は実行されない。 If it is determined in step S402 that there is no unapproved report, the recipe site server 31 finishes the process shown in FIG. That is, in this case, since there is no report that requires the receiver to approve, the process (S404 to S412) related to the approval request described below is not executed.
 ステップS402において未承認レポートがあると判定した場合、レシピサイトサーバ31はステップS403に進み、要承認要求レポートがあるか否かを判定する。すなわち、ステップS402で特定された未承認レポートに、不適レポート以外のレポートがあるか否かを判定する。なお、不適レポートは、不適フラグFiがONであるユーザによって投稿された作成レポートとして特定されるものである。
 ここで、処理対象のレシパによる投稿レシピを投稿先レシピとする未承認レポートのうち、不適レポートを除いた未承認レポートのことを「要承認要求レポート」と表記する。
 ステップS403において要承認要求レポートがないと判定した場合、レシピサイトサーバ31は図10に示す処理を終える。
If it is determined in step S402 that there is an unapproved report, the recipe site server 31 proceeds to step S403, and determines whether there is an approval request report. That is, it is determined whether or not there is a report other than the inappropriate report in the unapproved report specified in step S402. The inappropriate report is specified as a created report posted by a user whose inappropriate flag Fi is ON.
Here, among the non-approved reports in which the post recipe by the processing target receiver is the post-destination recipe, the non-approved report excluding the inappropriate report is referred to as “required approval request report”.
If it is determined in step S403 that there is no approval request report, the recipe site server 31 ends the process shown in FIG.
 一方、ステップS403において要承認要求レポートがあると判定した場合、レシピサイトサーバ31はステップS404に進んで要承認要求レポートの数を特定した上で、ステップS405で最古の要承認要求レポートの投稿日時を特定する。以下、該最古の要承認要求レポートの投稿日時のことを「最古投稿日時」と表記する。 On the other hand, if it is determined in step S403 that there is a request for approval request report, the recipe site server 31 proceeds to step S404, specifies the number of approval request reports required, and posts the oldest approval request report in step S405. Specify the date and time. Hereinafter, the posting date of the oldest approval request report is referred to as “oldest posting date”.
 ステップS405に続くステップ406でレシピサイトサーバ31は、処理対象レシパは遅滞傾向ユーザか否かを判定する。すなわち、遅滞傾向フラグFdがONであるユーザか否かを判定する。
 処理対象レシパが遅滞傾向ユーザでなければ、レシピサイトサーバ31はステップS407に進み、要承認要求レポート数が数閾値th1以上か否かを判定し、要承認要求レポート数が数閾値th1以上でなければ、ステップS408に進んで最古投稿日時からの経過時間が時間閾値TH1以上であるか否かを判定する。最古投稿日時からの経過時間が時間閾値TH1以上でなかった場合、レシピサイトサーバ31は図10に示す処理を終える。つまり、この場合は前述した(条件1)(条件2)の何れも成立していないため、承認要求は行われない。
In step 406 following step S405, the recipe site server 31 determines whether or not the processing target receiver is a user who tends to be late. That is, it is determined whether or not the user has the delay tendency flag Fd ON.
If the processing target receiver is not a delayed user, the recipe site server 31 proceeds to step S407, determines whether the number of approval request reports required is greater than or equal to the number threshold th1, and the number of approval request reports required must be greater than the number threshold th1. In step S408, it is determined whether the elapsed time from the oldest posting date is equal to or greater than the time threshold TH1. If the elapsed time from the oldest posting date / time is not equal to or greater than the time threshold TH1, the recipe site server 31 finishes the process shown in FIG. That is, in this case, since neither of (condition 1) and (condition 2) described above is satisfied, an approval request is not made.
 ステップS407において要承認要求レポート数が数閾値th1以上であった場合、又はステップS408で最古投稿日時からの経過時間が時間閾値TH1以上であった場合、レシピサイトサーバ31はステップS411に進み、要承認要求レポートについての承認要求処理を行う。すなわち、要承認要求レポートについての承認を要求する承認要求メールを処理対象レシパとしてのユーザに対して送信する処理を行う。
 この際、承認要求メールとしては、上述したチェックボックスcb1を設けた形式による電子メールを生成する。また、要承認要求レポートに、処理対象レシパにとっての非親密レポータからの投稿レポートが含まれている場合には、該当するレポータについての前述した登録チェックボックスcb2を設けた形式による電子メールを生成する。
If the number of approval request reports required in step S407 is greater than or equal to the threshold number th1, or if the elapsed time from the oldest posting date and time is greater than or equal to the time threshold value TH1 in step S408, the recipe site server 31 proceeds to step S411. Approval request processing for approval request report is performed. That is, a process for transmitting an approval request mail requesting approval for an approval request report to a user as a processing target receiver is performed.
At this time, as the approval request mail, an electronic mail in a format provided with the above-described check box cb1 is generated. If the approval request request report includes a post report from a non-intimate reporter for the processing target receiver, an e-mail is generated in a format provided with the registration check box cb2 for the corresponding reporter. .
 ステップS411の承認要求処理を実行したことに応じ、レシピサイトサーバ31はステップS412で承認要求日時の記憶処理を実行する。すなわち、ステップS411の処理で承認が要求された作成レポートのうち、承認の要求が初回であった作成レポートを対象として、該作成レポートのレポートIDに該作成レポートの承認要求日時(例えばステップS411の要求処理の実行日時)を対応づけてレポートDB34に記憶させる処理を行う。
 ステップS412の処理を実行したことに応じ、レシピサイトサーバ31は図10に示す処理を終える。
In response to the execution of the approval request process in step S411, the recipe site server 31 executes an approval request date storage process in step S412. That is, out of the created reports for which approval is requested in the process of step S411, the created report whose request for approval is the first time is targeted, the approval request date and time of the created report (for example, in step S411). The process of storing the request process execution date and time) in the report DB 34 is performed.
In response to the execution of the process of step S412, the recipe site server 31 ends the process shown in FIG.
 また、上述したステップS406において、処理対象レシパは遅滞傾向ユーザであると判定した場合、レシピサイトサーバ31はステップS409に進み、要承認要求レポート数が数閾値th2以上か否かを判定し、要承認要求レポート数が数閾値th2以上でなければ、ステップS410に進んで最古投稿日時からの経過時間が時間閾値TH2以上であるか否かを判定する。最古投稿日時からの経過時間が時間閾値TH2以上でなかった場合、レシピサイトサーバ31は図10に示す処理を終える。
 ここで、数閾値th2は、数閾値th1よりも小さな値であり、時間閾値TH2は時間閾値TH1よりも小さな値である。これにより、処理対象ユーザが遅滞傾向ユーザである場合は、通常よりも早いタイミングで承認要求が行われるようになる。
If it is determined in step S406 that the processing target receiver is a delayed user, the recipe site server 31 proceeds to step S409, determines whether the number of approval request reports required is equal to or greater than the number threshold th2, and If the number of approval request reports is not equal to or greater than the number threshold th2, the process proceeds to step S410 to determine whether or not the elapsed time from the oldest posting date is equal to or greater than the time threshold TH2. If the elapsed time from the oldest posting date / time is not equal to or greater than the time threshold value TH2, the recipe site server 31 ends the process shown in FIG.
Here, the number threshold th2 is smaller than the number threshold th1, and the time threshold TH2 is smaller than the time threshold TH1. Thereby, when the user to be processed is a user who tends to be late, an approval request is made at a timing earlier than usual.
 ステップS409において要承認要求レポート数が数閾値th2以上であった場合、又はステップS410で最古投稿日時からの経過時間が時間閾値TH2以上であった場合、レシピサイトサーバ31はステップS411の承認要求処理を実行し、続くステップS412の承認要求日時の記憶処理を実行した上で、図10に示す処理を終える。 If the number of approval request reports required in step S409 is equal to or greater than the number threshold th2, or if the elapsed time from the oldest posting date is equal to or greater than the time threshold TH2 in step S410, the recipe site server 31 requests the approval request in step S411. The processing is executed, and the storage processing of the approval request date and time in the subsequent step S412 is executed, and then the processing shown in FIG.
 図11は、自動承認に係る処理を示している。
 本例では、図11に示す処理としても、例えばバッチ処理により時間軸上で繰り返し行われる。
 図11において、レシピサイトサーバ31はステップS501で、処理対象レシパを特定する処理を行い、続くステップS502で未承認レポートがあるか否かを判定する。ステップS501、S502の処理は、それぞれ図10で説明したステップS401、S402と同様の処理である。
FIG. 11 shows processing related to automatic approval.
In this example, the processing shown in FIG. 11 is also repeatedly performed on the time axis by, for example, batch processing.
In FIG. 11, the recipe site server 31 performs a process of specifying a processing target receiver in step S <b> 501 and determines in step S <b> 502 whether there is an unapproved report. The processes in steps S501 and S502 are the same as the processes in steps S401 and S402 described with reference to FIG.
 ステップS502において未承認レポートがないと判定した場合、レシピサイトサーバ31は図11に示す処理を終える。つまり、この場合は自動承認すべきレポートは存在しないため、以下で説明する自動承認に係る処理(S504乃至S509)は実行されない。 If it is determined in step S502 that there is no unapproved report, the recipe site server 31 ends the process shown in FIG. That is, in this case, since there is no report that should be automatically approved, the process (S504 to S509) related to automatic approval described below is not executed.
 ステップS502において未承認レポートがあると判定した場合、レシピサイトサーバ31はステップS503に進み、要承認要求レポートがあるか否かを判定し、要承認要求レポートがないと判定した場合は図11に示す処理を終え、要承認要求レポートがあると判定した場合はステップS504に処理を進める。 If it is determined in step S502 that there is an unapproved report, the recipe site server 31 proceeds to step S503, determines whether there is an approval request report required, and if it is determined that there is no approval request report, FIG. If it is determined that there is an approval request report, the process proceeds to step S504.
 ステップS504でレシピサイトサーバ31は、要承認要求レポートの数(以下「D」と表記)を特定し、続くステップS505で処理対象レポート識別値dを初期値「0」にセットする。処理対象レポート識別値dは、要承認要求レポートのうち処理対象とする要承認要求レポートを識別するための値である。 In step S504, the recipe site server 31 identifies the number of approval request reports (hereinafter referred to as “D”), and in step S505, sets the processing target report identification value d to the initial value “0”. The process target report identification value d is a value for identifying an approval request report that is a process target among approval request reports.
 ステップS505に続くステップS506でレシピサイトサーバ31は、d番目レポートは親密レポータによる投稿レポートであるか否かを判定する。該判定は、d番目レポートのレポートIDとレポートDB34の記憶情報と処理対象レシパのユーザIDと親密情報DB55の記憶情報とに基づき行うことができる。具体的に、該判定は、d番目レポートのレポートIDとレポートDB34の記憶情報とに基づきd番目レポートの投稿レポータのユーザIDを特定し、該特定したユーザIDが、親密情報DB55の記憶情報において処理対象レシパのユーザIDと対応づけられているか否かを判定することで行う。 In step S506 following step S505, the recipe site server 31 determines whether the d-th report is a post report by an intimate reporter. This determination can be made based on the report ID of the d-th report, the storage information of the report DB 34, the user ID of the processing target receiver, and the storage information of the intimacy information DB 55. Specifically, the determination specifies the user ID of the posting reporter of the d th report based on the report ID of the d th report and the storage information of the report DB 34, and the specified user ID is stored in the storage information of the intimacy information DB 55. This is done by determining whether or not it is associated with the user ID of the processing target receiver.
 ステップS506において、d番目レポートは親密レポータによる投稿レポートでないと判定した場合、レシピサイトサーバ31は後述するステップS510に処理を進める。つまりこの場合、d番目レポートについての自動承認は行われない。 If it is determined in step S506 that the d-th report is not a post report by an intimate reporter, the recipe site server 31 advances the process to step S510 described later. That is, in this case, automatic approval for the d-th report is not performed.
 一方、ステップS506においてd番目レポートは親密レポータによる投稿レポートであると判定した場合、レシピサイトサーバ31はステップS507に進み、d番目レポートについての承認要求日時を特定する。具体的には、先のステップS412の処理によりレポートDB34に記憶された承認要求日時のうち、d番目レポートのレポートIDと対応づけられている承認要求日時を特定する。 On the other hand, if it is determined in step S506 that the d-th report is a post report by an intimate reporter, the recipe site server 31 proceeds to step S507 and specifies an approval request date and time for the d-th report. Specifically, the approval request date and time associated with the report ID of the d-th report among the approval request date and time stored in the report DB 34 by the processing of the previous step S412 is specified.
 ステップS507に続くステップS508でレシピサイトサーバ31は、特定した承認要求日時からの経過時間が一定時間以上であるか否かを判定し、該経過時間が一定時間以上でなければステップS510に処理を進め、該経過時間が一定時間以上であれば、ステップS509に進んでd番目レポートについての承認処理を行う。すなわち、レポートDB34においてd番目レポートのレポートIDと対応づけられている承認フラグFaをONとする処理を行う。 In step S508 following step S507, the recipe site server 31 determines whether or not the elapsed time from the specified approval request date and time is equal to or longer than a predetermined time. If the elapsed time is not equal to or longer than the predetermined time, the process proceeds to step S510. If the elapsed time is equal to or longer than the predetermined time, the process proceeds to step S509 to perform an approval process for the d-th report. That is, the process of turning ON the approval flag Fa associated with the report ID of the d-th report in the report DB 34 is performed.
 ステップS508に続くステップS509でレシピサイトサーバ31は、処理対象レポート識別値dが上述した「D」以上であるか否かを判定し、処理対象レポート識別値dが上述した「D」以上でなければ、ステップS511に進んで処理対象レポート識別値dを1インクリメントした上で、ステップS505に戻る。
 一方、処理対象レポート識別値dが上述した「D」以上であれば、レシピサイトサーバ31は図11に示す処理を終える。
In step S509 following step S508, the recipe site server 31 determines whether or not the processing target report identification value d is equal to or greater than “D” described above, and the processing target report identification value d must be equal to or greater than “D” described above. For example, the process proceeds to step S511, and the process target report identification value d is incremented by 1. Then, the process returns to step S505.
On the other hand, if the processing target report identification value d is equal to or greater than “D” described above, the recipe site server 31 ends the processing shown in FIG.
 図11に示す処理が繰り返し実行されることで、各レシパに対する要承認要求レポート(不適レポート以外の未承認レポート)のうち、親密レポータからの投稿レポートについては、承認要求日時からの経過時間に応じて自動承認が行われる。 By repeatedly executing the processing shown in FIG. 11, among reports requiring approval for each receiver (non-approved reports other than the non-appropriate report), the posting report from the intimate reporter depends on the elapsed time from the approval request date and time. Automatic approval.
 なお、上記では、親密度の評価として、ユーザDB32に記憶された行動履歴情報に基づく評価を行う例を挙げたが、親密度は、例えばレシピサイトとの間でユーザID(又はユーザ氏名等のユーザを識別可能な情報)が連携されたSNS(Social Networking Service)におけるユーザ間の友人関係情報(友人登録された関係にあるユーザを管理する情報)を用いて評価することもできる。或いは、レシピサイトサーバ31が例えばユーザ端末4等の所定の情報処理装置に記憶されている連絡帳(例えば電話帳や電子メールのアドレス帳)の情報にアクセス可能とされる場合には、該連絡帳の情報を用いて親密度を評価することもできる。例えば、レシパとしてのユーザが使用するユーザ端末4に記憶された連絡帳情報において対象とするレポータの氏名情報が登録されているか否かの情報を用いて、親密度を評価する等である。 In the above, an example of performing evaluation based on action history information stored in the user DB 32 has been given as evaluation of intimacy. However, intimacy is, for example, a user ID (or user name, etc.) with a recipe site. Evaluation can also be made using friendship information between users in SNS (Social Networking Service) in which user-identifiable information) is linked (information for managing users who are registered as friends). Alternatively, when the recipe site server 31 can access information in a contact book (for example, a phone book or an e-mail address book) stored in a predetermined information processing apparatus such as the user terminal 4, the contact is made. Intimacy can also be evaluated using information in the book. For example, the closeness is evaluated by using information on whether or not the name information of the target reporter is registered in the contact book information stored in the user terminal 4 used by the user as the receiver.
 また、上記では、不適レポータの判定にあたって行う投稿レポートの情報信頼度の評価として、投稿レポートに用いられる画像の類似度に基づく評価を行う例を挙げたが、該情報信頼度の評価としては、画像の類似度に基づく評価に限定されず、例えば投稿レポート間での文字の一致度合いに基づく評価を行うこともできる。例えば、文字の一致度合いが一定度合い以上の関係となっている作成レポートの数が多ければ、対象とするレポータは同一コメントを使い回している可能性が高いと推定され、該レポータによる投稿レポートは情報信頼度が低いと評価できる。或いは、対象とするレポータが対象とするレシピを閲覧(該レシピの閲覧が複数回の場合は最後の閲覧)してから該レシピに対する作成レポートを投稿するまでに要した時間の長さに基づく評価を行うこともできる。該時間が短い投稿レポートが多いほど、対象とするレポータによる投稿レポートの情報信頼度は低いと評価できる。 Moreover, in the above, as an evaluation of the information reliability of the posted report performed in the determination of the inappropriate reporter, an example of performing the evaluation based on the similarity of the images used in the posted report is given, but as the evaluation of the information reliability, The evaluation is not limited to the evaluation based on the similarity of images, and for example, the evaluation can be performed based on the matching degree of characters between the posting reports. For example, if there are a large number of created reports that have a certain degree of character matching or more, it is estimated that the target reporter is likely to use the same comment. It can be evaluated that information reliability is low. Alternatively, an evaluation based on the length of time required from posting the target recipe to the target reporter (last browsing if the recipe is viewed multiple times) to posting the creation report for the recipe Can also be done. It can be evaluated that the more posted reports with a shorter time, the lower the information reliability of the posted report by the target reporter.
 さらに、上記では、承認要求のタイミング調整にあたり行うレポート承認行動の分析として、レシパの承認済みレポートについての承認要求から承認を行うまでに要した時間を分析する例を挙げたが、該分析としては、過去に承認要求が行われた作成レポートの総数のうち未承認のまま放置されている作成レポートの数が占める割合を分析する等、他の手法による分析を行うこともできる。 Furthermore, in the above, as an analysis of the report approval action to be performed in order to adjust the timing of the approval request, an example was given in which the time taken from the approval request to the approval for the approved report of the receiver was analyzed. It is also possible to perform analysis using other methods, such as analyzing the ratio of the number of created reports left unapproved out of the total number of created reports for which approval requests have been made in the past.
 また、上記では、承認要求を電子メールにより行う場合を例示したが、承認要求は、レシピサイトにおける特定のウェブページ上での要求、又はユーザ端末4へのプッシュ通知による要求等として行うこともできる。 In the above, the case where the approval request is made by e-mail has been exemplified, but the approval request can also be made as a request on a specific web page at the recipe site, a request by a push notification to the user terminal 4, or the like. .
 また、上記では、レシパに対する承認要求をバッチ処理により行う例を挙げたが、レシパに対する承認要求は、該レシパによる投稿レシピに対するレポート投稿が行われるごとに行うこともできる。
 この場合、不適レポータの判定処理としても、該レシパによる投稿レシピに対するレポート投稿が行われるごとに行うことができる。
Moreover, although the example which performs the approval request | requirement with respect to a receiver by batch processing was mentioned above, the approval request | requirement with respect to a receiver can also be made whenever the report posting with respect to the posting recipe by this receiver is performed.
In this case, the determination process for the inappropriate reporter can be performed each time a report is posted to the posting recipe by the receiver.
[1-5.第1の実施の形態のまとめ]

 上記のように第1の実施の形態の情報処理装置(レシピサイトサーバ31)は、レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、レシパ、レポータそれぞれに紐付く情報に基づいて評価する親密度評価部(親密度評価処理部F1)を備える。
 また、親密度が一定度以上のレポータである親密レポータがレポートを投稿した場合は、レシパに当該レポートについての承認を要求した後、レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、親密度が一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、レシパに当該レポートについての承認を要求する一方で、時間経過に応じたレポート承認処理を行わない承認制御部(承認制御処理部F3)と、を備えている。
[1-5. Summary of First Embodiment]

As described above, the information processing apparatus (recipe site server 31) according to the first embodiment is a user who has posted a report on a recipe submitted by a recipe and a recipe that is a user who has posted a recipe on a website that posts a recipe. A familiarity evaluation unit (familiarity evaluation processing unit F1) that evaluates the familiarity with a certain reporter based on information associated with each of the receiver and the reporter is provided.
In addition, if an intimate reporter who is a reporter with a certain degree of intimacy submits a report, after requesting the reporter to approve the report, the report according to the passage of time without manual approval from the receiver When an approval process is performed and a non-intimate reporter who is a reporter whose intimacy is not more than a certain degree posts a report, the reporter is requested to approve the report, but the report approval process is not performed over time. An approval control unit (approval control processing unit F3).
 このような第1の実施の形態の情報処理装置によると、親密レポータの投稿レポートは時間経過に応じて自動承認されるため、それらのレポートについてレシパの承認の手間が省かれる。また、自動承認を行っていることで、レポートの掲載数の低下抑制を図ることが可能とされる。
 また、第1の実施の形態では、非親密レポータによるレポートは自動承認の対象外とされており、レシパによる手動承認が要求される。このため、掲載レポートの質悪化の抑制が図られる。
 さらに、上記のように非親密レポータによるレポートにレシパの手動承認を要求していることは、レシパに非親密レポータとのコミュニケーション機会を与えていることになるため、両者のコミュニケーション促進を図ることが可能とされる。そして、このようにコミュニケーション促進が図られることは、レシパと非親密レポータとの間の親密度向上に寄与し、次回に非親密レポータからレポート投稿があった際に当該レポートが自動承認される可能性が高まる。自動承認される可能性が高まることは、レシパのレポート承認に係る負担抑制に寄与するものである。
According to the information processing apparatus of the first embodiment, since the posting report of the intimate reporter is automatically approved as time elapses, it is possible to save time and effort for the approval of the receiver for these reports. In addition, by performing automatic approval, it is possible to suppress a decrease in the number of reports published.
In the first embodiment, the report by the non-intimate reporter is not subject to automatic approval, and manual approval by the receiver is required. For this reason, the deterioration of the quality of the posted report is suppressed.
Furthermore, as described above, requesting manual approval of a receiver in a report by a non-intimate reporter gives the receiver an opportunity to communicate with the non-intimate reporter. It is possible. In addition, the promotion of communication in this way contributes to the improvement of intimacy between the receiver and the intimate reporter, and the report can be automatically approved the next time a report is posted from the intimate reporter. Increases nature. Increasing the possibility of automatic approval contributes to reducing the burden associated with the reporter's report approval.
 上記のように第1の実施の形態によれば、レシパのレポート承認に係る負担を抑えながら、レポート掲載ページの質悪化の抑制とレポート掲載数の低下抑制との両立を図りつつ、レシパとレポータとの間のコミュニケーション促進を図ることができる。 As described above, according to the first embodiment, while reducing the burden associated with the reporter's report approval, the receiver and the reporter are able to simultaneously suppress the deterioration in the quality of the report publication page and the reduction in the number of report publications. Communication between them can be promoted.
 また、第1の実施の形態の情報処理装置においては、レポータが過去に投稿したレポートについての情報信頼度を評価した結果に基づき、レポータが不適レポータであるか否かを判定する不適レポータ判定部(不適レポータ判定処理部F2)を備え、承認制御部は、未承認の前記レポートについてレシパに承認を要求する前に、当該レポートが不適レポータにより投稿されたレポートである不適レポートか否かを判定し、不適レポートであると判定した場合は当該レポートについての承認を要求しない。 Further, in the information processing apparatus according to the first embodiment, the inappropriate reporter determination unit that determines whether or not the reporter is an inappropriate reporter based on the result of evaluating the information reliability of the report posted by the reporter in the past. (Appropriate Reporter Determination Processing Unit F2), and the approval control unit determines whether or not the report is an inappropriate report posted by the inappropriate reporter before requesting approval from the receiver for the unapproved report. However, if it is determined that the report is inappropriate, the report is not requested for approval.
 これにより、レシパが未承認のレポートのうちシステム側で事前に不適と判定されたレポータのレポートは承認が要求されない。このため、当該レポートについてレシパによる承認の手間が省かれる。
 従って、レシパのレポート承認に係る負担抑制効果を高めることができる。
As a result, reporter reports that have been previously determined to be unsuitable on the system side among reports not approved by the receiver are not required to be approved. This eliminates the need for approval by the receiver for the report.
Therefore, it is possible to enhance the burden suppressing effect related to the reporter approval of the receiver.
 さらに、第1の実施の形態の情報処理装置においては、不適レポータ判定部は、不適レポータであるか否かを、レポータが同一又は類似画像を用いたレポートを複数のレシピに対して投稿しているか否かに基づき判定している。 Furthermore, in the information processing apparatus according to the first embodiment, the inappropriate reporter determination unit posts a report using the same or similar images to a plurality of recipes as to whether or not the reporter is an inappropriate reporter. Judgment based on whether or not.
 これにより、レポートについての情報信頼度の評価として、レシピに対するレポートに適した評価を行うことが可能となり、不適レポータの判定精度の向上を図ることができる。 This makes it possible to perform an evaluation suitable for the report for the recipe as an evaluation of the information reliability of the report, and improve the determination accuracy of the inappropriate reporter.
 さらにまた、第1の実施の形態の情報処理装置においては、親密度評価部は、レシパによるレポータに対する過去のレポート承認回数に基づき親密度を評価している。 Furthermore, in the information processing apparatus according to the first embodiment, the familiarity evaluation unit evaluates the familiarity based on the past number of report approvals for the reporter by the receiver.
 レシパによるレポータに対する過去のレポート承認回数は、両者の間のコミュニケーション頻度を推し量る指標として機能する。従って、両者間の親密度を適切に評価することができ、親密の確度が比較的高いレポータを自動承認することができる。
 また、投稿レポートが自動承認されなかったレポータは、前記レシパへのレポート投稿を繰り返すうちに、その投稿レポートが自動承認されるように図られる。換言すれば、レシパは、同一レポータに対してレポート承認を繰り返すうち該レポータに対するレポート承認を行う手間が省かれるようになるものであり、この点においてレシパの承認に係る負担抑制が図られる。
The number of past report approvals for the reporter by the receiver functions as an index for estimating the frequency of communication between the two. Therefore, it is possible to appropriately evaluate the closeness between the two and automatically approve a reporter with a relatively high degree of intimacy.
Further, a reporter whose posting report has not been automatically approved is designed to automatically approve the posting report while repeating the posting of the report to the receiver. In other words, the reporter can save the trouble of performing report approval for the reporter while repeating report approval for the same reporter, and in this respect, the burden on the approval of the reporter can be reduced.
 また、第1の実施の形態の情報処理装置においては、親密度評価部は、レポータによる投稿レシピに対するレシパのレポート投稿回数に基づき親密度を評価している。 Further, in the information processing apparatus according to the first embodiment, the familiarity evaluation unit evaluates the familiarity based on the reporter's report posting count for the posting recipe by the reporter.
 レポータによる投稿レシピに対するレシパのレポート投稿回数としても、両者の間のコミュニケーション頻度を推し量る指標として機能する。
 従って、両者間の親密度を適切に評価することができ、親密の確度が比較的高いレポータを自動承認することができる。
The number of reporter submissions for the recipe submitted by the reporter also functions as an index for estimating the communication frequency between the two.
Therefore, it is possible to appropriately evaluate the closeness between the two and automatically approve a reporter with a relatively high degree of intimacy.
 さらに、第1の実施の形態の情報処理装置においては、親密度評価部は、レポータによる投稿レシピに対するレシパの投稿レポートについての承認回数に基づき親密度を評価している。 Furthermore, in the information processing apparatus according to the first embodiment, the familiarity evaluation unit evaluates the familiarity based on the number of approvals for the reporter posting report for the posting recipe by the reporter.
 これにより、レシパとレポータとの間の親密度がより適切に評価される。
 従って、親密の確度がさらに高いレポータを自動承認することができる。
Thereby, the familiarity between the receiver and the reporter is more appropriately evaluated.
Therefore, it is possible to automatically approve a reporter with a higher intimacy accuracy.
 さらにまた、第1の実施の形態の情報処理装置においては、承認制御部は、レシパの過去におけるレポート承認行動を分析した結果に基づき、承認を要求するタイミングを調整している。 Furthermore, in the information processing apparatus according to the first embodiment, the approval control unit adjusts the timing for requesting approval based on the result of analyzing the report approval behavior of the receiver in the past.
 これにより、例えばレポートへの承認が遅滞傾向にあるレシパには早めに承認を要求する等、レシパによるレポート承認行動の特性に応じた適切なタイミングにより承認要求を行うことが可能とされる。
 従って、承認が滞ることに伴いレシピサイトでのコミュニケーション機会が喪失されてしまう可能性の低減を図ることができる。
This makes it possible to make an approval request at an appropriate timing according to the characteristics of the report approval action by the receiver, such as, for example, requesting an earlier approval from a receiver whose report approval tends to be delayed.
Therefore, it is possible to reduce the possibility that a communication opportunity at the recipe site will be lost due to a delay in approval.
 また、第1の実施の形態の情報処理装置においては、承認制御部は、レシパの投稿レシピに対する投稿レポートとして複数の未承認レポートがある場合は、レシパに対する承認の要求として、個々の未承認レポートに対する承認指示操作が可能な形式による要求を行っている。 Further, in the information processing apparatus according to the first embodiment, the approval control unit, when there are a plurality of unapproved reports as posting reports for the recipe recipe of the receiver, each unapproved report as a request for approval for the receiver. A request is made in a format that allows an approval instruction operation.
 これにより、レシパによるレポート承認の容易性が増す。
 従って、レポート掲載数低下の抑制効果を高めることができる。また、レシパと非親密レポータとの間のコミュニケーション促進を図ることができる。
This increases the ease of report approval by the receiver.
Therefore, the effect of suppressing the reduction in the number of report publications can be enhanced. Further, communication between the receiver and the non-intimate reporter can be promoted.
 さらに、第1の実施の形態の情報処理装置においては、承認制御部は、レシパに対する承認の要求としてレポータの親密レポータへの登録指示操作が可能な形式による要求を行っている。 Furthermore, in the information processing apparatus according to the first embodiment, the approval control unit makes a request in a format that allows the reporter's intimate reporter to perform a registration instruction operation as an approval request to the receiver.
 これにより、レシパは非親密レポータを手動により親密レポータに登録することが可能とされる。
 十分な親密性を感じるか否かはレシパ個人の性格やレポータとのコミュニケーション内容等の条件で異なり得るものであり、コミュニケーションが僅かであっても十分な親密性が築かれるケースも想定され得る。このため、親密レポータの登録として、親密度に基づく自動登録のみでなく手動登録が可能とされることで、自動承認の対象者数の増加が見込まれる。
 従って、ユーザのレポート承認に係る手間の抑制効果を高めることができる。
This enables the receiver to manually register the non-intimate reporter with the intimate reporter.
Whether or not sufficient feeling of intimacy is felt may differ depending on the personality of the receiver and the contents of communication with the reporter, and there may be a case where sufficient intimacy is established even if there is little communication. For this reason, as the registration of the intimate reporter, not only automatic registration based on closeness but also manual registration is possible, so that the number of persons subject to automatic approval is expected to increase.
Therefore, it is possible to increase the effect of suppressing the trouble related to the user's report approval.
<2.第2の実施の形態>
[2-1.第2の実施の形態としての承認制御手法]

 続いて、第2の実施の形態について説明する。
 第2の実施の形態は、投稿レポートの掲載を、レシパによる承認、及びレシパからの返信入力を条件として行うものである。
 なお、第2の実施の形態において、ネットワークシステム1の構成は、レシピサイトサーバ31に代えてレシピサイトサーバ31Aが設けられた点が異なり、他の構成要素については第1の実施の形態の場合と同様である。
 第2の実施の形態において、既に第1の実施の形態で説明済みとなった部分については、特に断りがない限り、同一符号や同一ステップ番号を付して説明を省略する。
<2. Second Embodiment>
[2-1. Approval control method as the second embodiment]

Next, a second embodiment will be described.
In the second embodiment, posting a posting report is performed under the condition of approval by the receiver and input of a reply from the receiver.
In the second embodiment, the configuration of the network system 1 is different in that a recipe site server 31A is provided instead of the recipe site server 31, and the other components are the same as those in the first embodiment. It is the same.
In the second embodiment, the parts that have already been described in the first embodiment are denoted by the same reference numerals and the same step numbers and are not described unless otherwise specified.
 図12の機能ブロック図を参照して、レシピサイトサーバ31Aが実現する第2の実施の形態としての承認制御に係る各種機能について説明する。
 レシピサイトサーバ31Aは、レシピサイトサーバ31と比較して、承認制御処理部F3に代えて承認制御処理部F3Aを有する点が異なる。
With reference to the functional block diagram of FIG. 12, various functions relating to the approval control as the second embodiment realized by the recipe site server 31A will be described.
The recipe site server 31A differs from the recipe site server 31 in that it has an approval control processing unit F3A instead of the approval control processing unit F3.
 承認制御処理部F3Aは、レシパに対する承認の要求として、未承認レポートに対する返信入力が可能な形式による要求を行う。この際、レシパの投稿レシピに対する投稿レポートに複数の未承認レポートがあれば、承認制御処理部F3Aは承認の要求として、個々の未承認レポートに対する返信入力が可能な形式による要求を行う。 The approval control processing unit F3A makes a request in a format that allows a reply input to an unapproved report as an approval request to the receiver. At this time, if there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, the approval control processing unit F3A makes a request in a format that allows a reply input to each unapproved report.
 図13を参照して、第2の実施の形態における承認要求について説明する。
 図13では、承認制御処理部F3Aがレシパに送信する送信要求メールとして、承認を要求すべき未承認レポートが複数であった場合に対応した送信要求メールの例を示している。
 この場合の送信要求メールは、図6に示した送信要求メールと比較して、未承認レポートごとにコメント入力欄rpが設けられた点が異なる。コメント入力欄rpは、対応する未承認レポートについての返信コメントを入力するための欄であり、レシパとしてのユーザは該コメント入力欄rpにテキスト入力を行うことができる。
 ユーザは、送信要求メールに設けられた送信ボタンB1を操作することで、コメント入力欄rpに入力したテキスト情報を、対応する未承認レポートに対する返信情報としてレシピサイトサーバ31Aに返信することができる。
With reference to FIG. 13, an approval request in the second embodiment will be described.
FIG. 13 shows an example of a transmission request mail corresponding to a case where there are a plurality of unapproved reports that should be requested for approval as a transmission request mail transmitted to the receiver by the approval control processing unit F3A.
The transmission request mail in this case is different from the transmission request mail shown in FIG. 6 in that a comment input field rp is provided for each unapproved report. The comment input field rp is a field for inputting a reply comment for the corresponding unapproved report, and a user as a receiver can enter text in the comment input field rp.
The user can return the text information input in the comment input field rp to the recipe site server 31A as return information for the corresponding unapproved report by operating the transmission button B1 provided in the transmission request mail.
 上記のように、承認の要求として、個々の未承認レポートに対する返信入力が可能な形式による要求を行うことで、投稿レポートに対する返信入力の容易性が増し、レポート掲載数低下の抑制効果を高めることができる。また、レシパと非親密レポータとの間のコミュニケーション促進も図られる。 As mentioned above, by making a request in a format that allows reply input to individual unapproved reports as approval requests, the ease of reply input to posted reports is increased, and the effect of suppressing the reduction in the number of reports published is increased. Can do. In addition, communication between the receiver and non-intimate reporter is promoted.
 また、承認制御処理部F3Aは、承認され且つレシパからの返信入力が行われたレポートであることを条件に、レポートがレシピサイトに掲載されるように制御を行う。
 第2の実施の形態のレシピサイト運営システム3では、投稿されレポートDB34に登録された各作成レポートのレポートIDには、前述した承認フラグFaと共に返信フラグFrが対応づけられる。返信フラグFrは、ON(例えば「1」)が返信済、OFF(例えば「0」)が未返信を表す。本例では、返信フラグFrはレポートDB34においてレポートIDごとに記憶される。
Further, the approval control processing unit F3A performs control so that the report is posted on the recipe site on condition that the report is approved and a reply input from the receiver is performed.
In the recipe site management system 3 according to the second embodiment, the reply flag Fr is associated with the report flag of each created report that has been posted and registered in the report DB 34 together with the approval flag Fa described above. In the reply flag Fr, ON (for example, “1”) indicates that the reply has been completed, and OFF (for example, “0”) indicates that the reply has not been made. In this example, the reply flag Fr is stored for each report ID in the report DB 34.
 ここで、第2の実施の形態において、レシピサイトサーバ31Aは、対象とするレシピに対する投稿レポートをレシピサイトに掲載するにあたっては、それらの投稿レポートのうち、承認フラグFaと返信フラグFrの双方がONである投稿レポートのみを掲載する。
 この前提の下で、承認制御処理部F3Aは、第1の実施の形態における承認制御処理部F3と同様に、レシパの操作入力に応じた承認処理、及び親密レポータの投稿レポートについての自動的な承認処理を行って、承認フラグFaをONとする。
 さらに、承認制御処理部F3Aは、例えば上述したような承認要求メールにおけるコメント入力欄rpに返信情報が入力され、該入力された返信情報を受信したことに応じて、該コメント入力欄rpに対応する未承認レポートについての返信フラグFrをONとする処理を行う。
 これにより、承認され且つレシパからの返信入力が行われたレポートがレシピサイトに掲載されるようになる。
Here, in the second embodiment, when the recipe site server 31A publishes a posting report for a target recipe on the recipe site, both the approval flag Fa and the reply flag Fr are included in the posting reports. Only posting reports that are ON will be posted.
Under this premise, the approval control processing unit F3A automatically performs the approval processing according to the operation input of the receiver and the posting report of the intimate reporter in the same manner as the approval control processing unit F3 in the first embodiment. Approval processing is performed and the approval flag Fa is set to ON.
Further, the approval control processing unit F3A, for example, responds to the comment input field rp when the reply information is input to the comment input field rp in the approval request mail as described above and the input reply information is received. Processing for turning on the reply flag Fr for the unapproved report to be performed is performed.
As a result, a report that has been approved and for which a reply from the receiver has been input is posted on the recipe site.
[2-2.処理手順]

 上記により説明した第2の実施の形態としての承認制御手法を実現するための処理について説明する。
 レシピサイトサーバ31Aとしても、レシピサイトサーバ31と同様、先の図7乃至図11に示した処理と同様の処理を実行する。
 但しこの場合、図10に示したステップS411の承認要求処理では、先の図13に示したように未承認レポート(本例では要承認要求レポート)に対し返信コメントを入力するためのコメント入力欄rpを設けた形式による送信要求メールを生成して処理対象レシパとしてのユーザに送信する処理を行う。この際、処理対象レシパの投稿レシピに対する投稿レポートに複数の要承認要求レポートがあれば、承認制御処理部F3Aは個々の要承認要求レポートに対しコメント入力欄rpを設けた形式による承認要求メールを生成・送信する。
[2-2. Processing procedure]

Processing for realizing the approval control method as the second embodiment described above will be described.
Similarly to the recipe site server 31, the recipe site server 31A executes the same processing as the processing shown in FIGS.
However, in this case, in the approval request process in step S411 shown in FIG. 10, a comment input field for inputting a reply comment to the unapproved report (in this example, a request for approval request report) as shown in FIG. A process for generating a transmission request mail in a format provided with rp and transmitting it to a user as a processing target receiver is performed. At this time, if there are a plurality of approval request reports in the submission report for the recipe of the processing target receiver, the approval control processing unit F3A sends an approval request mail in a format in which a comment input field rp is provided for each approval request report. Generate and send.
 第2の実施の形態におけるレシピサイトサーバ31Aは、図14に示す処理を実行する。
 なお、図14に示す処理は、レシピサイトサーバ31AにおけるCPU101が例えばレシピサイトサーバ31AにおけるROM102や記憶部108等の所定の記憶装置に記憶されたプログラムに基づき実行する。
The recipe site server 31A in the second embodiment executes the process shown in FIG.
14 is executed by the CPU 101 in the recipe site server 31A based on a program stored in a predetermined storage device such as the ROM 102 or the storage unit 108 in the recipe site server 31A.
 図14において、レシピサイトサーバ31AはステップS601で、投稿レポートへの返信があったか否かを判定する。すなわち、ステップS411で送信した送信要求メールに対する返信情報、具体的には該送信要求メールにおける送信ボタンB1が操作されることに伴い受信した該送信要求メールへの入力情報に、コメント入力欄rpに対する入力情報が含まれているか否かを判定する。 In FIG. 14, the recipe site server 31A determines in step S601 whether or not there is a reply to the posted report. That is, the reply information to the transmission request mail transmitted in step S411, specifically, the input information to the transmission request mail received in response to the operation of the transmission button B1 in the transmission request mail is added to the comment input field rp. It is determined whether or not input information is included.
 ステップS601において投稿レポートへの返信がなかったと判定した場合、レシピサイトサーバ31Aは図14に示す処理を終える。
 一方、ステップS601において投稿レポートへの返信があったと判定した場合、レシピサイトサーバ31AはステップS602に進み、該当するレポートについての返信設定処理を行う。すなわち、ステップS601で入力情報の受信が確認されたコメント入力欄rpに対応する作成レポートを特定し、該特定した作成レポートのレポートIDと対応づけられてレポートDB34に記憶されている返信フラグFrをONとする処理を行う。
 ステップS602の処理を実行したことに応じ、レシピサイトサーバ31Aは図14に示す処理を終える。
If it is determined in step S601 that there is no reply to the posted report, the recipe site server 31A ends the process shown in FIG.
On the other hand, if it is determined in step S601 that there is a reply to the posted report, the recipe site server 31A proceeds to step S602 and performs a reply setting process for the corresponding report. That is, the created report corresponding to the comment input field rp for which the reception of the input information has been confirmed in step S601 is specified, and the reply flag Fr stored in the report DB 34 in association with the report ID of the specified created report is set. Processing to turn on is performed.
In response to the execution of the process of step S602, the recipe site server 31A ends the process shown in FIG.
 なお、上記では、投稿レポートに対するレシパの返信入力として、テキスト入力を受け付ける例を示したが、該返信入力としては、返信内容が定型の内容とされた情報である定型返信情報の入力を受け付けることもできる。
 定型返信情報としては、例えば定型文や、スタンプ等の画像による情報を挙げることができる。この場合における返信入力の受け付けとしては、レシパに提示した複数種類の定型返信情報について、レシパからの任意の定型返信情報の選択入力を受け付ける等の形態により行うことが可能である。
In the above, an example is shown in which text input is received as a reply input of a receiver for a posted report. However, as the reply input, input of standard reply information that is information in which the reply contents are standard contents is accepted. You can also.
As the fixed reply information, for example, information by an image such as a fixed sentence or a stamp can be cited. In this case, the reply input can be received in a form such as accepting a selection input of arbitrary standard reply information from the receiver for a plurality of types of standard reply information presented to the receiver.
 上記のような定型返信情報による返信入力が可能とされることで、レシパは、投稿レポートへの返信入力を例えば定型文やスタンプ等の入力で済ませることが可能とされる。
 従って、投稿レポートをサイトに掲載させるにあたってのレシパの負担抑制を図ることができる。
By enabling the reply input based on the standard reply information as described above, the receiver can complete the reply input to the posting report by inputting, for example, a standard sentence or a stamp.
Therefore, it is possible to reduce the burden on the receiver when posting the posted report on the site.
[2-3.第2の実施の形態のまとめ]

 上記のように第2の実施の形態の情報処理装置(レシピサイトサーバ31A)においては、承認制御部(承認制御処理部F3A)は、承認され且つレシパからの返信入力が行われたレポートであることを条件に、レポートがウェブサイトに掲載されるように制御を行っている。
[2-3. Summary of Second Embodiment]

As described above, in the information processing apparatus (recipe site server 31A) according to the second embodiment, the approval control unit (approval control processing unit F3A) is a report that is approved and a reply is input from the receiver. As a result, the report is controlled to be posted on the website.
 これにより、投稿レポートを掲載させるにあたり、レシパはレポートに対する返信という形式でのコミュニケーションをレポータに対してとることが必須とされる。
 従って、レポート掲載ページがレシパとレポータとの間のコミュニケーションの場としてより活性化することに寄与できる。
As a result, when posting a posted report, it is essential for the reporter to communicate with the reporter in the form of a reply to the report.
Therefore, it is possible to contribute to the activation of the report posting page as a place for communication between the receiver and the reporter.
 また、第2の実施の形態の情報処理装置においては、承認制御部は、レシパの投稿レシピに対する投稿レポートに複数の未承認レポートがある場合は、レシパに対する承認の要求として、個々の未承認レポートに対する返信入力が可能な形式による要求を行っている。 Further, in the information processing apparatus of the second embodiment, the approval control unit, when there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver, each unapproved report as a request for approval for the receiver. A request is made in a format that allows reply input to.
 これにより、投稿レポートに対する返信入力の容易性が増す。
 従って、レポート掲載数低下の抑制効果を高めることができる。また、レシパと非親密レポータとの間のコミュニケーション促進を図ることができる。
This increases the ease of inputting a reply to the posted report.
Therefore, the effect of suppressing the reduction in the number of report publications can be enhanced. Further, communication between the receiver and the non-intimate reporter can be promoted.
 さらに、第2の実施の形態の情報処理装置においては、承認制御部は、返信入力として、返信内容が定型の内容とされた情報である定型返信情報の入力を受け付けている。 Furthermore, in the information processing apparatus according to the second embodiment, the approval control unit accepts input of standard reply information, which is information in which the reply content is a standard content, as a reply input.
 これによりレシパは、投稿レポートへの返信入力を例えば定型文やスタンプ等の入力で済ませることが可能とされ、投稿レポートをサイトに掲載させるにあたってのレシパの負担抑制を図ることができる。
As a result, the receiver can complete the reply input to the posted report by, for example, inputting a fixed sentence or a stamp, and can reduce the burden on the receiver when posting the posted report on the site.
<3.プログラム及び記憶媒体>

 以上、本発明に係る情報処理装置の実施の形態としてのレシピサイトサーバ(31又は31A)を説明してきたが、実施の形態のプログラムは、該レシピサイトサーバの処理を情報処理装置(CPU等)に実行させるプログラムである。
<3. Program and Storage Medium>

As mentioned above, although the recipe site server (31 or 31A) as embodiment of the information processing apparatus which concerns on this invention has been demonstrated, the program of embodiment carries out the process of this recipe site server (CPU etc.). This is a program to be executed.
 実施の形態のプログラムは、レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価機能と、前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御機能と、を情報処理装置に実現させる。
 すなわち、このプログラムは、例えばレシピサイトサーバ31等の情報処理装置に図7乃至図11等により説明した処理を実行させるプログラムに相当する。
The program according to the embodiment provides the intimacy between a reporter who is a user who has posted a recipe on a website for posting a recipe and a reporter who is a user who has posted a report on a recipe posted by the recipe, and the reporter and the reporter, respectively. If the intimacy reporter who evaluates based on the information associated with the report and the intimacy reporter who is a reporter whose intimacy is a certain degree or more posts the report, after requesting the reporter to approve the report, Even if there is no manual approval from the receiver, a report approval process corresponding to the passage of time is performed, and when a non-intimate reporter that is a reporter whose intimacy is not more than the predetermined level submits a report, the report is sent to the receiver Requesting approval for a report, but not approving report approval over time. Realizing control functions and the information processing apparatus.
That is, this program corresponds to a program that causes an information processing apparatus such as the recipe site server 31 to execute the processes described with reference to FIGS.
 このようなプログラムにより、上述したレシピサイトサーバ31(又は31A)としての情報処理装置を実現できる。
 そして、このようなプログラムはコンピュータ装置等の機器に内蔵されている記憶媒体としてのHDDや、CPUを有するマイクロコンピュータ内のROM等に予め記憶しておくことができる。或いはまた、半導体メモリ、メモリーカード、光ディスク、光磁気ディスク、磁気ディスクなどのリムーバブル記憶媒体に、一時的あるいは永続的に格納(記憶)しておくことができる。またこのようなリムーバブル記憶媒体は、いわゆるパッケージソフトウェアとして提供することができる。
 また、このようなプログラムは、リムーバブル記憶媒体からパーソナルコンピュータ等にインストールする他、ダウンロードサイトから、LAN、インターネットなどのネットワークを介してダウンロードすることもできる。
By such a program, the information processing apparatus as the recipe site server 31 (or 31A) described above can be realized.
Such a program can be stored in advance in an HDD as a storage medium built in a device such as a computer device, a ROM in a microcomputer having a CPU, or the like. Alternatively, it can be stored (stored) temporarily or permanently in a removable storage medium such as a semiconductor memory, memory card, optical disk, magneto-optical disk, or magnetic disk. Such a removable storage medium can be provided as so-called package software.
Further, such a program can be installed from a removable storage medium to a personal computer or the like, or can be downloaded from a download site via a network such as a LAN or the Internet.
<4.変形例>

 本発明は上記により説明した具体例に限定されず、各種の変形例が考えられる。
 例えば、親密レポータの登録に係る制御機能として、レシパによる操作に応じ親密レポータの登録解除を行う機能が付加されてもよい。これにより、誤操作や一時の気の迷い等により登録されてしまった親密レポータの投稿レポートについて、レシパの意に反した自動承認が行われてしまうことの防止を図ることができる。
<4. Modification>

The present invention is not limited to the specific examples described above, and various modifications can be considered.
For example, as a control function related to the registration of the intimate reporter, a function of canceling the registration of the intimate reporter according to an operation by the receiver may be added. As a result, it is possible to prevent an automatic approval against the intention of the receiver from being performed on the posting report of the intimate reporter that has been registered due to an erroneous operation or a temporary distraction.
 1 ネットワークシステム、2 ネットワーク、3、3A レシピサイト運営システム、31、31A レシピサイトサーバ、32 ユーザDB(データベース)、33 レシピDB、34 レポートDB、35 親密情報DB、4 ユーザ端末、101 CPU、F1 親密度評価処理部、F2 不適レポータ判定処理部、F3、F3A 承認制御処理部、Ar1 レシピ名掲載領域、Ar2 料理写真掲載領域、Ar3 材料・分量掲載領域、Ar4 調理手順掲載領域、Ar5 レポート掲載領域、cb1 承認チェックボックス、cb2 登録チェックボックス、B1 送信ボタン、rp コメント入力欄 1 network system, 2 networks, 3 and 3A recipe site management system, 31 and 31A recipe site server, 32 user DB (database), 33 recipe DB, 34 report DB, 35 intimate information DB, 4 user terminal, 101 CPU, F1 Intimacy evaluation processing section, F2 inappropriate reporter determination processing section, F3, F3A approval control processing section, Ar1 recipe name posting area, Ar2 cooking photo posting area, Ar3 ingredients / quantity posting area, Ar4 cooking procedure posting area, Ar5 report posting area , Cb1 approval check box, cb2 registration check box, B1 send button, rp comment input field

Claims (15)

  1.  レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価部と、
     前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御部と、を備える
     情報処理装置。
    Based on information associated with each of the receiver and the reporter, the intimacy between the reciper who posted the recipe on the website posting the recipe and the reporter who is the user who posted the report for the recipe posted by the reciper. A closeness evaluation unit to be evaluated;
    If an intimate reporter who is a reporter whose intimacy is greater than a certain degree posts the report, after requesting the reporter to approve the report, the reporter responds to the passage of time without manual approval from the reporter. When a non-intimate reporter who is a reporter whose intimacy is not equal to or greater than a certain degree has posted a report, the reporter is requested to approve the report, while the reporter responds to the passage of time. An information processing apparatus comprising: an approval control unit that does not perform report approval processing.
  2.  前記レポータが過去に投稿したレポートについての情報信頼度を評価した結果に基づき、前記レポータが不適レポータであるか否かを判定する不適レポータ判定部を備え、
     前記承認制御部は、
     未承認の前記レポートについて前記レシパに承認を要求する前に、当該レポートが前記不適レポータにより投稿されたレポートである不適レポートか否かを判定し、前記不適レポートであると判定した場合は当該レポートについての承認を要求しない
     請求項1に記載の情報処理装置。
    An inappropriate reporter determination unit that determines whether or not the reporter is an inappropriate reporter based on a result of evaluating information reliability of a report posted by the reporter in the past;
    The approval control unit
    Before requesting approval of the reporter for the unapproved report, it is determined whether the report is an inappropriate report that is a report posted by the inappropriate reporter, and if it is determined that the report is the inappropriate report, the report The information processing apparatus according to claim 1, wherein no approval is requested.
  3.  前記不適レポータ判定部は、
     前記不適レポータであるか否かを、前記レポータが同一又は類似画像を用いたレポートを複数のレシピに対して投稿しているか否かに基づき判定する
     請求項1に記載の情報処理装置。
    The inappropriate reporter determination unit
    The information processing apparatus according to claim 1, wherein whether or not the reporter is inappropriate is determined based on whether or not the reporter has posted reports using the same or similar images to a plurality of recipes.
  4.  前記親密度評価部は、
     前記レシパによる前記レポータに対する過去のレポート承認回数に基づき前記親密度を評価する
     請求項1に記載の情報処理装置。
    The intimacy evaluation unit
    The information processing apparatus according to claim 1, wherein the closeness is evaluated based on a past report approval count for the reporter by the receiver.
  5.  前記親密度評価部は、
     前記レポータによる投稿レシピに対する前記レシパのレポート投稿回数に基づき前記親密度を評価する
     請求項1に記載の情報処理装置。
    The intimacy evaluation unit
    The information processing apparatus according to claim 1, wherein the closeness is evaluated based on a report posting number of the recipe for a posting recipe by the reporter.
  6.  前記親密度評価部は、
     前記レポータによる投稿レシピに対する前記レシパの投稿レポートについての承認回数に基づき前記親密度を評価する
     請求項5に記載の情報処理装置。
    The intimacy evaluation unit
    The information processing apparatus according to claim 5, wherein the closeness is evaluated based on the number of times of approval for the report report of the recipe for the posting recipe by the reporter.
  7.  前記承認制御部は、
     前記レシパの過去におけるレポート承認行動を分析した結果に基づき、前記承認を要求するタイミングを調整する
     請求項1に記載の情報処理装置。
    The approval control unit
    The information processing apparatus according to claim 1, wherein a timing for requesting the approval is adjusted based on a result of analyzing the report approval behavior of the receiver in the past.
  8.  前記承認制御部は、
     前記レシパの投稿レシピに対する投稿レポートとして複数の未承認レポートがある場合は、前記レシパに対する承認の要求として、個々の未承認レポートに対する承認指示操作が可能な形式による要求を行う
     請求項1に記載の情報処理装置。
    The approval control unit
    The request according to a format in which an approval instruction operation for each unapproved report is performed as a request for approval for the receiver when there are a plurality of unapproved reports as a posting report for the recipe recipe of the receiver. Information processing device.
  9.  前記承認制御部は、
     前記レシパに対する承認の要求として前記レポータの前記親密レポータへの登録指示操作が可能な形式による要求を行う
     請求項1に記載の情報処理装置。
    The approval control unit
    The information processing apparatus according to claim 1, wherein the request is made in a format in which a registration instruction operation of the reporter to the intimate reporter can be performed as an approval request for the receiver.
  10.  前記承認制御部は、
     承認され且つ前記レシパからの返信入力が行われたレポートであることを条件に、前記レポートが前記ウェブサイトに掲載されるように制御を行う
     請求項1に記載の情報処理装置。
    The approval control unit
    The information processing apparatus according to claim 1, wherein control is performed so that the report is posted on the website on condition that the report is approved and a reply input from the receiver is performed.
  11.  前記承認制御部は、
     前記レシパの投稿レシピに対する投稿レポートに複数の未承認レポートがある場合は、前記レシパに対する承認の要求として、個々の未承認レポートに対する前記返信入力が可能な形式による要求を行う
     請求項10に記載の情報処理装置。
    The approval control unit
    The request according to a format in which the reply input for each unapproved report can be made as a request for approval for the receiver when there are a plurality of unapproved reports in the posting report for the recipe recipe of the receiver. Information processing device.
  12.  前記承認制御部は、
     前記返信入力として、返信内容が定型の内容とされた情報である定型返信情報の入力を受け付ける
     請求項10に記載の情報処理装置。
    The approval control unit
    The information processing apparatus according to claim 10, wherein an input of fixed reply information that is information in which a reply content is fixed is received as the reply input.
  13.  レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価ステップと、
     前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御ステップと、を情報処理装置が実行する
     情報処理方法。
    Based on information associated with each of the receiver and the reporter, the intimacy between the reciper who posted the recipe on the website posting the recipe and the reporter who is the user who posted the report for the recipe posted by the reciper. A familiarity evaluation step to evaluate;
    If an intimate reporter who is a reporter whose intimacy is greater than a certain degree posts the report, after requesting the reporter to approve the report, the reporter responds to the passage of time without manual approval from the reporter. When a non-intimate reporter who is a reporter whose intimacy is not equal to or greater than a certain degree has posted a report, the reporter is requested to approve the report, while the reporter responds to the passage of time. An information processing method in which an information processing apparatus executes an approval control step that does not perform report approval processing.
  14.  レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価機能と、
     前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御機能と、を情報処理装置に実現させる
     プログラム。
    Based on information associated with each of the receiver and the reporter, the intimacy between the reciper who posted the recipe on the website posting the recipe and the reporter who is the user who posted the report for the recipe posted by the reciper. A closeness evaluation function to evaluate,
    If an intimate reporter who is a reporter whose intimacy is greater than a certain degree posts the report, after requesting the reporter to approve the report, the reporter responds to the passage of time without manual approval from the reporter. When a non-intimate reporter who is a reporter whose intimacy is not equal to or greater than a certain degree has posted a report, the reporter is requested to approve the report, while the reporter responds to the passage of time. A program that allows an information processing device to implement an approval control function that does not perform report approval processing.
  15.  レシピを掲載するウェブサイトにレシピを投稿したユーザであるレシパと、前記レシパによる投稿レシピに対するレポートを投稿したユーザであるレポータとの親密度を、前記レシパ、前記レポータそれぞれに紐付く情報に基づいて評価する親密度評価機能と、
     前記親密度が一定度以上のレポータである親密レポータが前記レポートを投稿した場合は、前記レシパに当該レポートについての承認を要求した後、前記レシパからの手動による承認がなくても時間経過に応じたレポート承認処理を行い、前記親密度が前記一定度以上でないレポータである非親密レポータがレポートを投稿した場合は、前記レシパに当該レポートについての承認を要求する一方で、前記時間経過に応じたレポート承認処理を行わない承認制御機能と、を情報処理装置に実現させるプログラムを記憶した
     記憶媒体。
    Based on information associated with each of the receiver and the reporter, the intimacy between the reciper who posted the recipe on the website posting the recipe and the reporter who is the user who posted the report for the recipe posted by the reciper. A closeness evaluation function to evaluate,
    If an intimate reporter who is a reporter whose intimacy is greater than a certain degree posts the report, after requesting the reporter to approve the report, the reporter responds to the passage of time without manual approval from the reporter. When a non-intimate reporter who is a reporter whose intimacy is not equal to or greater than a certain degree has posted a report, the reporter is requested to approve the report, while the reporter responds to the passage of time. A storage medium that stores an approval control function that does not perform report approval processing and a program that causes an information processing device to realize the approval control function.
PCT/JP2016/074231 2016-08-19 2016-08-19 Information processing device, information processing method, program and storage medium WO2018034000A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2016/074231 WO2018034000A1 (en) 2016-08-19 2016-08-19 Information processing device, information processing method, program and storage medium
JP2017551734A JP6254753B1 (en) 2016-08-19 2016-08-19 Information processing apparatus, information processing method, program, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/074231 WO2018034000A1 (en) 2016-08-19 2016-08-19 Information processing device, information processing method, program and storage medium

Publications (1)

Publication Number Publication Date
WO2018034000A1 true WO2018034000A1 (en) 2018-02-22

Family

ID=60860177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/074231 WO2018034000A1 (en) 2016-08-19 2016-08-19 Information processing device, information processing method, program and storage medium

Country Status (2)

Country Link
JP (1) JP6254753B1 (en)
WO (1) WO2018034000A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6931959B1 (en) * 2021-02-26 2021-09-08 クックパッド株式会社 Recipe search support device, recipe search support method, and recipe search support program

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6384978B1 (en) * 2018-02-19 2018-09-05 クックパッド株式会社 Server apparatus, distribution method, and program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013228892A (en) * 2012-04-26 2013-11-07 Rakuten Inc Information processing apparatus, information processing method, information processing program, and recording medium
JP2014154003A (en) * 2013-02-12 2014-08-25 Nec Personal Computers Ltd Information processing device, control method and program

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013228892A (en) * 2012-04-26 2013-11-07 Rakuten Inc Information processing apparatus, information processing method, information processing program, and recording medium
JP2014154003A (en) * 2013-02-12 2014-08-25 Nec Personal Computers Ltd Information processing device, control method and program

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KEI AOKI: "Kigyo to Shohisha no Kyoso Katsudo ni Okeru, Sankasha no Motivation ni Kansuru Kenkyu", MARKETING JOURNAL, vol. 35, no. 4, 31 March 2016 (2016-03-31), pages 105 - 125, ISSN: 2188-1669 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6931959B1 (en) * 2021-02-26 2021-09-08 クックパッド株式会社 Recipe search support device, recipe search support method, and recipe search support program
WO2022180946A1 (en) * 2021-02-26 2022-09-01 クックパッド株式会社 Recipe search support device, recipe search support method, and recipe search support program
JP2022131610A (en) * 2021-02-26 2022-09-07 クックパッド株式会社 Recipe search support device, recipe search support method, and recipe search support program

Also Published As

Publication number Publication date
JP6254753B1 (en) 2017-12-27
JPWO2018034000A1 (en) 2018-08-16

Similar Documents

Publication Publication Date Title
US8843463B2 (en) Providing content by using a social network
TWI530882B (en) Information push method, server, user terminal, and system
US20120209685A1 (en) Check-ins to commercial venues
WO2014052260A2 (en) Systems, methods and interfaces for evaluating an online entity presence
US9734519B2 (en) Native advertisement smart injection
US9542504B2 (en) Metanodes for open graph protocols
US20230186339A1 (en) Method and System for Sharing Personal Information with Web Sites
US20170351733A1 (en) User address match based on match quality
WO2016189743A1 (en) Information processing device, information processing method, program, and storage medium
US20150058419A1 (en) Server device, information disclosure control method, and recording medium
JP6254753B1 (en) Information processing apparatus, information processing method, program, and storage medium
US10382914B2 (en) Techniques to leverage data from mobile headers
CN110879870A (en) Page redirection method and device based on HTTP request
JP6052714B1 (en) Introduction system and introduction method
WO2021005808A1 (en) Information processing device, information processing method, and program
US20210142351A1 (en) Online friend referral system
TW201635210A (en) Information processing device, information processing method, program, storage medium
US20210067508A1 (en) Certification System
KR20150109234A (en) method of defining relation of invitation between users for application and server and system thereof
JP5736293B2 (en) Evaluation server, terminal device, information processing system, information processing method, and program
US20160041983A1 (en) Local query ranking for search assist method and apparatus
JP6038414B1 (en) Information processing apparatus, information processing method, program, and storage medium
US20150019622A1 (en) On time launcher for sites
KR20180037794A (en) Korean wave online contents development and trading system and method
KR20240047255A (en) User matching service for child-care

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2017551734

Country of ref document: JP

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

Ref document number: 16913528

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16913528

Country of ref document: EP

Kind code of ref document: A1