JP2022148850A - Information processing method - Google Patents

Abstract

To provide an information processing method capable of recruiting a wide range of participants for predetermined activities.SOLUTION: The information processing method includes the steps of: receiving, from user terminals, first information of a data amount equal to or less than a predetermined value including a string, a font, a color, and a background color representing a predetermined activity in which multiple persons participate; and publishing a web page that introduces predetermined activities created based on the first information.SELECTED DRAWING: Figure 4

Description

The present disclosure relates to an information processing method for publishing an event plan.

Disclosed is a technique for accepting input of plan information including activity plan content and presenting plan information including a second type plan content related to the first type plan to the planner of the first type plan content. (for example, Patent Document 1).

JP 2016-085692 A

An object of the present disclosure is to provide an information processing method capable of widely recruiting participants in a predetermined activity.

One aspect of the present disclosure is
receiving, from a user terminal, first information having a data amount equal to or less than a predetermined value and including character strings, character fonts, character colors, and background colors representing a predetermined activity in which a plurality of people participate;
Publishing a web page introducing the predetermined activity created based on the first information;
It is an information processing method including

According to the present disclosure, it is possible to recruit a wide range of participants for a given activity.

FIG. 1 is a diagram showing an example of the system configuration of an event planning system according to the first embodiment. FIG. 2 is an example of the hardware configuration of the center server and user terminals. FIG. 3 is a diagram showing an example of functional configurations of a center server and user terminals. FIG. 4 is an example of information held in the event information database. FIG. 5 is an example of an event registration screen of a user terminal. FIG. 6 is an example of an event list screen of the user terminal. FIG. 7 is an example of a flowchart of event registration processing of a user terminal. FIG. 8 is an example of a flowchart of processing of the center server.

For example, when a plan for an event is introduced on the web or the like, an image or the like of the event may be used in addition to the explanation of the content of the event. By using an image image in the introduction of the event plan, the user who sees the introduction is more likely to have an image of the event. However, the image of the event may give unnecessary preconceptions to the user who saw the introduction, and may hinder participation in the event.

One of the aspects of the present disclosure is to send a data amount of a predetermined value or less, including character strings, character fonts, character colors, and background colors, expressing a predetermined activity in which a plurality of people participate, from a user terminal. and publishing a web page introducing a predetermined activity created based on the first information.

The information processing method is executed by an information processing apparatus. The information processing device is, for example, a computer such as a server. The server may be, for example, a web server. The information processing apparatus includes, for example, a control unit such as a processor, and the control unit executes the information processing method. Predetermined activities in which a plurality of people participate include, for example, an event held by gathering a predetermined number of people at a predetermined place, an event distributed on the web, crowdfunding, and the like. Events include, for example, dinner parties, experience meetings, consultation meetings, lectures, classrooms, concerts, and tours.

According to one aspect of the present disclosure, the predetermined activity is represented by any one of a character string, character font, character color, and background color, and published on the web. The data amount of the first information representing the predetermined activity is limited to a predetermined value or less, which is very small compared to image data, for example. That is, the predetermined activity is represented by a small amount of information such as characters, fonts of characters, character colors, and background colors. As a result, it is possible to suppress unnecessary preconceptions about the predetermined activity from being given to the user who has browsed the web page introducing the predetermined activity, and to recruit more participants for the predetermined activity.

In addition, the present disclosure provides an information processing apparatus that executes the information processing method described above, a program for causing a computer to execute the information processing method described above, or a non-temporary storage medium that stores the program in a computer-readable form. can also be captured.

Embodiments of the present disclosure will be described below based on the drawings. The configurations of the following embodiments are examples, and the present disclosure is not limited to the configurations of the embodiments.

<First Embodiment>
FIG. 1 is a diagram showing an example of the system configuration of an event planning system 100 according to the first embodiment. The event planning system 100 is a system that publishes an event planned by a user and supports recruiting participants for the event. In the first embodiment, an event is an activity that gathers a predetermined number of people at a predetermined place. Specifically, the event includes a dinner party, an experience meeting, a consultation meeting, a lecture, a classroom, a concert, a tour, and the like. Also, the event may be held on the web. An event is an example of a "predetermined activity."

The event planning system 100 includes a center server 1 and user terminals 2 . Although only one user terminal 2 is shown in FIG. 1, the event planning system 100 includes a plurality of user terminals.

The center server 1 and the user terminal 2 are each connected to a network N1 and can communicate with each other through the network N1. Network N1 is, for example, the Internet.

A client application program of the event planning system 100 is installed in the user terminal 2 . When the user of the user terminal 2 organizes the event, information about the event is input to the event registration screen of the user terminal 2 . The information about the event includes, for example, the name of the event, the name of the planning user of the event, the area where the event is held, the font of the character string indicating the name of the event, the background color, the character color, and the like. Information about an event is hereinafter referred to as event information. Among the event information, information for expressing the image of the event such as the font, character color, and background color of the character string indicating the event name is referred to as image information. Event information is an example of "first information".

In the first embodiment, the data amount of event information is equal to or less than a predetermined value. This is because, in the first embodiment, the use of image data, moving image data, etc. is not permitted in order to express the image of the event. That is, in the first embodiment, the use of one-dimensional information such as characters is permitted to express the image of the event, but the use of two-dimensional or higher information such as images and moving images is not permitted. . Therefore, the data amount of the event information is, for example, a predetermined value or less, which is smaller than the data amount of the image data. The predetermined value is, for example, 100 kilobytes to 500 kilobytes. This prevents the information about the image of the event from becoming excessive, and prevents the event from giving unnecessary preconceptions.

The user terminal 2 transmits an event disclosure request to the center server 1 . Event information is also sent to the center server 1 together with the event disclosure request. When the center server 1 receives an event publication request from the user terminal 2, the center server 1 publishes the event information of the event on the website of the event planning system 100. FIG.

Publishing event information means, for example, posting the plan of the event on a web page provided by the event planning system 100 . In the first embodiment, event planning is published on a web page provided by event planning system 100 based on event information. Since the event information is limited information represented by a character string indicating the event name, character font, character color, and background color, the user should not be given unnecessary preconceptions about the event. As a result, it is possible to recruit a wide range of participants for the event. A web page that posts an event plan is an example of a "web page that introduces a predetermined activity."

FIG. 2 shows an example of the hardware configuration of the center server 1 and the user terminal 2. As shown in FIG. The center server 1 includes a CPU 101, a memory 102, an external storage device 103, and a communication section 104 as a hardware configuration. The memory 102 and the external storage device 103 are computer-readable recording media.

The external storage device 103 stores various programs and data used by the CPU 101 when executing each program. The external storage device 103 is, for example, an EPROM (Erasable Programmable ROM) or a hard disk drive. The programs held in the external storage device 103 include, for example, an operating system (OS), a control program for the event planning system 100, and various other application programs.

The memory 102 is a storage device that provides the CPU 101 with a storage area and a work area for loading programs stored in the external storage device 103 and is used as a buffer. The memory 102 is, for example, ROM (Read Only Memory), RAM (Random
including semiconductor memory such as Access Memory).

The CPU 101 executes various processes by loading the OS and various application programs stored in the external storage device 103 into the memory 102 and executing them. The number of CPUs 101 is not limited to one, and a plurality of CPUs may be provided.

The communication unit 104 is, for example, a wired network card such as a LAN (Local Area Network) or a dedicated line, and connects to the network N1 through an access network such as the LAN. The hardware configuration of the center server 1 is not limited to that shown in FIG.

The user terminal 2 includes, for example, a CPU 201, a memory 202, an external storage device 203, a wireless communication section 204, and a touch panel display 205 as a hardware configuration. However, in FIG. 2, hardware related to the event planning system 100 is extracted and displayed, and the hardware configuration of the user terminal 2 is not limited to that shown in FIG.

The CPU 201, the memory 202, and the external storage device 203 are the same as the CPU 101, the memory 102, and the external storage device 103, respectively, so descriptions thereof will be omitted. A client application program for the event planning system 100 is stored in the external storage device 203 .

The wireless communication unit 204 is, for example, a wireless communication circuit compatible with mobile communication systems such as 5G (5th Generation), LTE (Long Term Evolution), LTE-Advanced, and 3G, or wireless communication systems such as WiFi. be. The wireless communication unit 204 connects to an access network by wireless communication, and connects to the network N1 through the access network.

The touch panel display 205 is an example of an input device and an output device. For example, a user operation is input to the touch panel display 205 and the content of the user operation is output to the CPU 201 . Further, the touch panel display 205 displays image data according to instructions from the CPU 201 .

FIG. 3 is a diagram showing an example of functional configurations of the center server 1 and the user terminal 2. As shown in FIG. The user terminal 2 includes a control unit 21 and a screen data storage unit 22 as functional configurations. These functional components are achieved by the CPU 201 of the user terminal 2 executing the client application program of the event planning system 100, for example.

Through the touch panel display 205 , the control unit 21 receives user operation input for transmission of, for example, an event disclosure request, a viewing request, and a participation request. The control unit 21 transmits, for example, an event disclosure request, viewing request, participation request, or the like to the center server 1 through the wireless communication unit 204 . Further, the control unit 21 reads a screen corresponding to a user's operation and data received from the center server 1 from the screen data storage unit 22 and causes the touch panel display 205 to output the screen.

The screen data storage unit 22 is created in the storage area of the external storage device 203 . The screen data storage unit 22 holds screen data in the client application program of the event planning system 100 . Details of the processing of the control unit 21 and details of the screen data held in the screen data storage unit 22 will be described later.

Next, the center server 1 has a control unit 11, a user information DB 12, and an event information DB 13 as functional configurations. These functional configurations are achieved, for example, by the CPU 101 of the center server 1 executing the control program of the event planning system 100 stored in the external storage device 103 .

The control unit 11 manages user information and event information. The control unit 11 receives, for example, an event disclosure request, viewing request, and participation request from the user terminal 2 through the communication unit 104 . Event information is also received along with the event publication request.

Upon receiving an event publication request, the control unit 11 publishes the event plan on the website of the event planning system 100 . Specifically, the control unit 11 registers the event information received together with the event disclosure request in the event information DB 13 . Further, when receiving an event viewing request, the control unit 11 reads event information registered in the event information DB 13 and creates an event list page. The event list page is a page for introducing event plans. That is, in the first embodiment, an event plan is made public when event information is registered in the event information DB 13 and posted on the event list page.

A user information DB 12 and an event information DB 13 are created in the storage area of the external storage device 103 . The user information DB 12 holds user information about users. The user information held in the user information DB 12 includes, for example, user identification information, account name, activity area, and planned event identification information. The event information DB 13 holds event information about events. Details of the information held in the event information DB 13 will be described later. The functional configurations of the center server 1 and user terminals 2 are not limited to the example shown in FIG.

FIG. 4 is an example of information held in the event information DB 13. As shown in FIG. The event information DB 13 stores event information about events. One record of the event information DB 13 corresponds to event information of one event. One record of the event information DB 13 includes, for example, fields of event ID, project user ID, event name, font, character color, background color, and participating user ID.

The event ID field stores event identification information. The event identification information is uniquely given in the event planning system 100 by the control unit 11, for example. The user identification information of the user who planned the event is stored in the planning user ID field. The event name field stores a character string indicating the event name. The font field stores information indicating the font of the character string indicating the event name. Information indicating the color of the character string indicating the event name is stored in the character color field. The background color field stores information indicating the background color. User identification information of users participating in the event is stored in the participating user ID field.

The information indicating the font, character color, and background color may each be a code, for example. The information held in the event information DB 13 shown in FIG. 4 is an example, and the information held in the event information DB 13 is not limited to the example shown in FIG. For example, if the event information includes the area where the event is held, the field of the event area may be included in the field of one record of the event information DB 13 .

5 and 6 are screen examples of the user terminal 2. FIG. FIG. 5 is an example of an event registration screen of the user terminal 2. As shown in FIG. The event registration screen is a screen for inputting information when drafting an event. The event registration screen is displayed by menu operation, for example.

The event registration screen includes, for example, an event name input field, an event name font selection button, a character color selection button, and a background color selection button. You can enter text up to the maximum number of characters in the event name input field. The font, character color, and background color can be selected by selecting options prepared for each of the font, character color, and background color. The selected font, character color, and background color may be reflected in the event name entry field of the information.

Also, on the event registration screen shown in FIG. 5, a publish button and a save button are provided in the upper part of the screen. When the public button is selected, a user operation requesting public disclosure of the event is input to the user terminal 2 , and the control unit 21 of the user terminal 2 transmits the public request for the event and the event information to the center server 1 . The event information transmitted to the center server 1 at this time includes, for example, the event name, user identification information of the user of the user terminal 2 as the user who planned the event, and image information. The image information includes information indicating the font, character color, and background color specified on the event registration screen. The information indicating the font, character color, and background color may be, for example, corresponding codes. A default value is set for each of the font, character color, and background color, and the default value is used when not specified by the user.

Upon receiving an event disclosure request from the user terminal 2, the control unit 11 of the center server 1 adds event identification information to the event and registers the event information in the event information DB 13 (see FIG. 4).

As shown in FIG. 5, the event registration screen is not provided with means for registering image data, video data, and the like. The event registration screen is provided only with means for selecting a character string indicating the event name, character font, character color, and background color. As a result, the data amount of the event information is limited to be smaller than the data amount of the image data or the like. Note that the upper limit of event information may be explicitly set. In this case, the upper limit of the event information is set to a value between 100 kilobytes and 500 kilobytes so as to be a smaller value than the image data. Note that the event registration screen shown in FIG. 5 is an example, and the configuration of the event registration screen can be changed as appropriate according to the embodiment.

FIG. 6 is an example of an event list screen of the user terminal 2. As shown in FIG. The event list screen is a screen for displaying a list of published event plans. The event list screen is displayed by menu operation, for example.

The event list screen includes a display column for each event. The display fields for each event include, for example, an event name display field, a planning user's account name, and a participation request button. The event name display column displays the event name included in the event information of the event in the font, character color, and background color included in the event information.

When the participation request button is selected, a user operation requesting participation in the event is input to the user terminal 2 . The control unit 21 of the user terminal 2 transmits a participation request to the event to the center server 1 when the user operation of the participation request is input. For example, user identification information and relevant event identification information are also transmitted along with the request to participate in the event. Upon receiving the event participation request from the user terminal 2, the control unit 11 of the center server 1 updates the record of the event in the event information DB 13 (FIG. 5).

<Process flow>
FIG. 7 is an example of a flowchart of event registration processing of the user terminal 2 . The process shown in FIG. 7 is repeatedly executed, for example, in the user terminal 2 while the client application program of the event planning system 100 is being executed. 7 is executed by the CPU 201 of the user terminal 2, but for the sake of convenience, functional components will be mainly described.

In OP101, the control unit 21 determines whether or not the event registration screen has been activated. The event registration screen is activated, for example, by inputting an event registration menu operation to the user terminal 2 . If the event registration screen has been activated (OP101: YES), the process proceeds to OP102. If the event registration screen has not been activated (OP101: NO), the processing shown in FIG. 7 ends.

In OP102, the control unit 21 receives a user operation input to the event registration screen. User operations input to the event registration screen include, for example, inputting an event name, selecting a font, character color, and background color.

In OP103, the control unit 21 determines whether or not a user operation to select the public button has been input. If a user operation to select the public button is input (OP103: YES), the process proceeds to OP104. If the user operation to select the public button has not been input (OP103: NO), the process proceeds to OP105.

In OP<b>104 , the control unit 21 transmits an event disclosure request and event information to the center server 1 . After that, the processing shown in FIG. 7 ends.

In OP105, the control unit 21 determines whether or not a user operation to select the save button has been input. If a user operation to select the save button is input (OP105: YES), the process proceeds to OP106. If the user operation to select the save button has not been input (OP105: NO), the process proceeds to OP103.

In OP106, the control unit 21 saves the content entered in the event registration screen. The content entered on the event registration screen is saved in a predetermined storage area of the external storage device 203, for example. After that, the processing shown in FIG. 7 ends. Note that the processing shown in FIG. 7 is an example, and can be changed as appropriate according to the embodiment.

FIG. 8 is an example of a flow chart of processing of the center server 1 . The processing shown in FIG. 8 is repeatedly executed at a predetermined cycle. 8 is executed by the CPU 101 of the center server 1, but for the sake of convenience, the description will focus on the functional components.

In OP 201 , the control unit 11 determines whether or not an event disclosure request has been received from the user terminal 2 . If an event disclosure request is received from the user terminal 2 (OP201: YES), the process proceeds to OP202. If an event disclosure request has not been received from the user terminal 2 (OP201: NO), the process proceeds to OP203.

In OP202, the control unit 11 registers the event information received together with the event disclosure request in the event information DB 13. FIG. As a result, the event becomes a public event. After that, the processing shown in FIG. 8 ends.

In OP 203 , the control unit 11 determines whether or not an event viewing request has been received from the user terminal 2 . If an event viewing request is received from the user terminal 2 (OP203: YES), the process proceeds to OP204. If an event viewing request has not been received from the user terminal 2 (OP203: NO), the process proceeds to OP206.

In OP204, the control unit 11 reads the event information from the event information DB 13 and creates a web page of the event list. In OP205, the control unit 11 transmits the created event list web page to the user terminal 2. FIG. After that, the processing shown in FIG. 8 ends.

In OP206, the control unit 11 determines whether or not a request to participate in the event has been received from the user terminal 2. If a request to participate in the event has been received (OP206: YES), the process proceeds to OP207. If no event participation request has been received from the user terminal 2 (OP206: NO), the process shown in FIG. 8 ends.

In OP 207 , the control unit 11 updates the event information DB 13 in response to the event participation request received from the user terminal 2 . For example, the control unit 11 adds the user identification information received with the participation request to the participating user ID field of the record corresponding to the event identification information received with the participation request in the event information DB 13 (FIG. 4). After that, the processing shown in FIG. 8 ends.

<Action and effect of the first embodiment>
In the first embodiment, when an event is published on the web, the character string indicating the event name is displayed in the font, character color, and background color specified by the user who planned the event. published in the form In the first embodiment, an event is expressed with a minimum amount of information without using images, moving images, and the like. As a result, it is possible to suppress unnecessary preconceptions about the event from being given to users viewing information about the event, and to recruit a wide range of participants.

<Other embodiments>
The above-described embodiment is merely an example, and the present disclosure can be modified as appropriate without departing from the scope of the present disclosure.

In the first embodiment, character font, character color, and background color are used as information for expressing the image of the event, but the information for expressing the image of the event includes character size, Modifications such as bold, italics, and underlining may also be used.

The event planning system 100 according to the first embodiment is intended for planning events that are actually held by a plurality of people. It can also be applied to activities such as funding that are conducted by a plurality of operating users.

The processes and means described in the present disclosure can be freely combined and implemented as long as there is no technical contradiction.

Also, the processing described as being performed by one device may be shared and performed by a plurality of devices. Alternatively, processes described as being performed by different devices may be performed by one device. In a computer system, it is possible to flexibly change the hardware configuration (server configuration) to implement each function.

The present disclosure can also be implemented by supplying a computer program implementing the functions described in the above embodiments to a computer, and reading and executing the program by one or more processors of the computer. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. A non-transitory computer-readable storage medium is any type of disk such as, for example, a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), Including read only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards, flash memory, optical cards, any type of medium suitable for storing electronic instructions.

Reference Signs List 1 Center server 2 User terminal 11 Control unit 12 User information database 13 Event information database 21 Control unit 22 Screen data storage unit 100 Event planning system 101, 201 CPU
102, 202... Memory 103, 203... External storage device 104... Communication unit 204... Wireless communication unit 205... Touch panel display

Claims (1)

receiving, from a user terminal, first information having a data amount equal to or less than a predetermined value and including character strings, character fonts, character colors, and background colors representing a predetermined activity in which a plurality of people participate;
Publishing a web page introducing the predetermined activity created based on the first information;
Information processing method including.

Images