Image acquisition system and program

Abstract

At an event, the organizer can easily collect images owned by the guests. [Solution] The image collection system comprises a request unit for the event organizer to request the guests of the event to upload images related to the event, for each group, and a storage unit for storing the images uploaded by the guests based on the request, for each group.

Description

Technical Field

[0001] The present invention relates to an image collection system and a program.

Background Art

[0002] Conventionally, a system for assisting in sending invitations to guests has been proposed for holding events such as wedding receptions and secondary parties (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In recent years, at events, effects such as projecting images such as photos and videos related to the host or guests onto a screen, or publishing them in paper items such as booklets and message cards distributed from the bride and groom to guests on the wedding day may be performed. In this case, it is preferable if not only the images held by the host but also the images held by the guests can be easily collected from the guests, as the effect of the production can be enhanced.

[0005] An object of the present invention is to provide an image collection system and a program that can easily collect images held by guests from the guests by the host at an event.

Means for Solving the Problems

[0006] One aspect of the present invention is an image collection system for an event in which the event organizer manages the guests of the event in groups, comprising: a request unit that requests the guests of the event to upload images related to the event, group by group; and a storage unit that stores the images uploaded by the guests based on the request, group by group.

[0007] One aspect of the present invention is a program that causes a computer to perform the following actions for an event in which the event organizer manages the guests of the event in groups: request the guests of the event to upload images related to the event, group by group; and save the images uploaded by the guests in accordance with the request, group by group. [Effects of the Invention]

[0008] According to the present invention, the organizer can easily collect images owned by the guest from the guest. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the device configuration of the event management system according to this embodiment. [Figure 2] This figure shows an example of the functional configuration of the event management system of this embodiment. [Figure 3] This figure shows an example of the operation flow of the event management system of this embodiment. [Figure 4] This figure shows an example of the guest list registration screen in this embodiment. [Figure 5] This figure shows an example of the guest list screen in this embodiment. [Figure 6] This figure shows an example of the photo sharing settings screen of this embodiment. [Figure 7] This figure shows an example of the guidance text editing screen of this embodiment. [Figure 8] This figure shows an example of the invitation screen of this embodiment. [Figure 9] This figure shows an example of a photo sharing request screen according to this embodiment. [Figure 10] This figure shows an example of the browsing screen of this embodiment. [Figure 11] This figure shows an example of the photo viewing screen of this embodiment. [Figure 12] This figure shows an example of the reminder operation screen of this embodiment. [Figure 13] This figure shows an example of the text of the registration completion email for this embodiment. [Modes for carrying out the invention]

[0010] Next, the event management system 1 of this embodiment will be described with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the embodiments described below. In all the figures used to illustrate the embodiments, components with the same function are given the same reference numerals, and repeated explanations are omitted. Furthermore, in this application, "based on XX" means "based on at least XX," and includes cases where it is based on another element in addition to XX. Also, "based on XX" is not limited to cases where XX is used directly, but also includes cases where it is based on something that has been calculated or processed from XX. "XX" is any element (for example, any information).

[0011] (Embodiment) Figure 1 shows an example of the device configuration of the event management system 1 of this embodiment. The event management system 1 comprises a guest terminal device 10, an organizer terminal device 20, and an event management device 30.

[0012] The guest terminal device 10, the organizer terminal device 20, and the event management device 30 can communicate with each other via the network NT. The network NT includes the Internet, WAN (Wide Area Network), LAN (Local Area Network), public line, provider device, dedicated line, wireless base station, and the like.

[0013] The event management system 1 can be connected via the network NT to the invitation printing server 40 of the invitation printing system 4 operated by a printing company or the like.

[0014] In the case where there are multiple guests G for the event, one guest terminal device 10 may be used for each guest G. For example, when sending invitations to n guests G (n is a natural number), the guest terminal device 10 used by the first guest G is also described as the guest terminal device 10-1. Similarly, the guest terminal device 10 used by the nth guest G is also described as the guest terminal device 10-n.

[0015] The event management device 30 functions as an arithmetic unit that operates a program to be processed by the guest terminal device 10 and the organizer terminal device 20, and a storage unit that stores data. For example, the event management device 30 functions as a so-called cloud server that provides various functions of the event management system 1. Note that some of the functions of the event management device 30 described below may be provided in the guest terminal device 10 or the organizer terminal device 20. That is, in the following description, some of the functions described as functions provided by the event management device 30 may be functions provided by the guest terminal device 10 or the organizer terminal device 20.

[0016] Both the guest terminal device 10 and the organizer terminal device 20 are computer devices such as so-called personal computers, tablets, and smartphones. The guest terminal device 10 includes a display unit 11 such as a liquid crystal display, an operation unit 12 such as a keyboard or touch panel, a processing unit 13 such as a CPU (Central Processing Unit), and a storage unit 14 such as semiconductor memory or a hard disk drive. Similarly, the organizer terminal device 20 includes a display unit 21, an operation unit 22, a calculation unit 23, and a storage unit 24.

[0017] [Functional Configuration and Operation of Event Management System 1] Event Management System 1 can be used to manage invitations for various events, as long as they are invitation-only events. In one example of this embodiment, the event is a wedding reception or a so-called after-party following the reception. The organizer H is the couple getting married. Organizer H intends to invite their family, relatives, school friends, colleagues (e.g., coworkers and superiors), and other people with whom they have a connection as guests G.

[0018] Furthermore, organizer H may want to send electronic invitations to guest G via network NT. On the other hand, organizer H may want to send printed paper invitations to guest G, for example, a guest of honor or a guest G who is a supervisor at work. In this way, the organizer H can choose between an electronic invitation (hereinafter also referred to as a web invitation) or a paper invitation (hereinafter also referred to as a paper invitation) depending on the guest G.

[0019] Figure 2 shows an example of the functional configuration of the event management system 1 of this embodiment. Figure 3 shows an example of the operation flow of the event management system 1 of this embodiment. The following details of the functions of the event management system 1 will be explained with reference to Figures 2 and 3.

[0020] [Create a guest list] (Step S210) Organizer H operates the organizer terminal device 20 to create a guest list. The guest list is a compilation of information on guests G invited to the event hosted by organizer H.

[0021] Figure 4 shows an example of the guest list registration screen P1 of this embodiment. The guest list registration screen P1 is an image that displays summary information such as the number of guests G listed in a list format. The guest list registration screen P1 functions as the top screen when creating a guest list.

[0022] The display control unit 304 of the event management device 30 transmits information (display information 52) for displaying the guest list registration screen P1 to the organizer terminal device 20. The organizer terminal device 20 displays the guest list registration screen P1 on the display unit 21.

[0023] The guest list registration screen P1 includes the guest count screens P11 and P12. The guest count screens P11 and P12 display the number of guests G that each couple intends to invite, grouped by their respective guests. For example, if a couple, A and B, are inviting guests G to an event (e.g., a wedding reception) as organizers H, the guest count screen P11 will display the number of guests G that A is inviting. The guest count screen P12 will display the number of guests G that B is inviting.

[0024] If the organizer H wants to check the breakdown of guests G, they operate the guest count screen P11 (or guest count screen P12; the same applies in the following explanation) to display the guest list screen P2. When the display control unit 304 detects an operation by the organizer H on the guest count screen P11, it displays the guest list screen P2.

[0025] Figure 5 shows an example of the guest list screen P2 in this embodiment. The guest list screen P2 is a screen for displaying a list of guests G and for editing (also called updating) the information of guests G. The guest list screen P2 contains a group tab P21, an individual guest screen P22, an add guest button P23, and an invitation settings button P24.

[0026] The Group tab P21 is an interactive image for selecting the group to which Guest G belongs. A group is a classification of Guest G based on their attributes, such as family, relatives, friends, colleagues, or other people with whom they have a connection. In this embodiment, a group is also referred to as a "community."

[0027] The delivery medium selection unit 302 selects the type of delivery medium for a guest G by associating the types (groups) of guest G, which are managed in multiple categories, with the types of delivery media.

[0028] In other words, the event management system 1 manages guests G by dividing them into multiple groups (or communities). Therefore, according to the event management system 1, when the relationship between organizer H and guest G differs for each community, the relationship can be managed collectively on a community basis, thereby reducing the management effort required from organizer H.

[0029] It should be noted that among the guests G (for example, relatives or acquaintances), the organizer H may know their email or SNS (Social Networking Service; also known as Social media or Direct Message) addresses, but not their official names or addresses. In such cases, the event management system 1 can invite them using a nickname (for example) instead of their official name.

[0030] The individual guest screen P22 displays a list of abbreviations for each guest G. Here, the abbreviation for guest G can be the guest G's full name, just the surname, just the given name, or a nickname used by the organizer H to refer to guest G. In other words, the abbreviation for guest G does not necessarily have to be their formal name. The individual guest screen P22 includes images showing how to delete guest G and images showing how to edit guest G's details (edit button P221). The "Add Guest" button (P23) is an image showing how to add a new guest (G) to a group (community).

[0031] When the edit button P221 or the guest add button P23 is pressed, the display control unit 304 displays a guest editing screen (not shown), which is an image for editing the detailed information of an individual guest G, on the display unit 21.

[0032] The organizer terminal device 20 transmits the guest list created based on the operations of organizer H described above to the event management device 30 as invitee information 51.

[0033] (Step S310) When the calculation unit 300 of the event management device 30 receives the invitee information 51 from the organizer terminal device 20, it stores it in the storage unit 390 as a guest list.

[0034] [Creating invitation data] Once the guest list is created, the next step is to edit the contents of the invitation. The event management system 1 of this embodiment provides various functions for creating and sending invitation data.

[0035] Organizer H operates the organizer terminal device 20 to select (or edit) the invitation design. Selecting (or editing) the invitation design is also called creating the invitation. The invitation design can be selected separately for paper invitations and web invitations. We will now explain the workflow in more detail for two cases: when paper invitations are selected, and when web invitations are selected. Note that illustrations of the invitation design editing screen will be omitted.

[0036] [If paper invitations are selected] If paper invitations are selected, the event management system 1 will: (1) Types of paper invitations (2) Whether or not to provide a paper copy for reply (3) Whether or not to print a reply code on the paper invitation It provides various setting functions such as those mentioned above.

[0037] [1: Choosing the type of paper invitation] Organizer H can choose the type of paper invitation for each guest G (or group). The types of paper invitations include the paper type (e.g., thickness, color, folding method, Japanese paper, Western paper, etc.) and the design of the text side of the invitation (e.g., Japanese style, Western style, vertical writing, horizontal writing, presence or absence of illustrations, type of illustrations, etc.). The organizer terminal device 20 transmits the type of paper invitation selected by organizer H to the event management device 30. The invitation information acquisition unit 301 of the event management device 30 stores the type of paper invitation selected by organizer H in the storage unit 390 for each guest G (or each group).

[0038] [2: Setting whether or not a reply form is required] The paper invitation can include a reply form for guest G to respond to organizer H regarding their attendance at the event. A reply form refers to, for example, a postcard addressed to the organizer H and indicating the means of payment for the return postage (e.g., postage stamps or a postage-paid indication). The reply form may also have the guest G's name pre-printed on it. If a reply form is enclosed with the paper invitation, Guest G will fill in whether they will attend or not on the reply form (for example, a postcard) and return it to Organizer H. Whether or not a reply form is available can be set by the organizer H using the organizer terminal device 20. The invitation information acquisition unit 301 acquires whether or not the reply form medium set by the organizer H is required.

[0039] In other words, the types of mailing media include paper invitations (paper media). When a paper invitation is selected as the type of mailing medium, the invitation information acquisition unit 301 acquires information about guest G, using at least one of the following items as input items: the type of paper invitation and whether or not a reply form is required.

[0040] [3: Print settings for reply-to codes] The event management system 1 provides a setting function to determine whether or not to print a reply code on paper invitations. By printing a reply code on the paper invitation, guest G can respond to the invitation by reading the reply code with the guest terminal device 10. The reply code is information readable by the guest terminal device 10, such as a two-dimensional code indicating the reply address on the computer system (e.g., URL: Uniform Resource Locator). In this example, the guest terminal device 10 is equipped with an imaging unit such as a camera, and by imaging the reply address code printed on the paper invitation, it displays the web page of the reply address indicated by the reply address code on the display unit 11.

[0041] With the event management system 1 configured in this way, guests G can reduce the effort required to respond to paper invitations using paper media (e.g., reply postcards). Furthermore, organizers H can reduce the effort required to manually input attendance and other information received from guests G via paper replies into the event management system 1.

[0042] [If a web invitation is selected] If a web invitation is selected, the event management system 1 will: (1) Types of transmission and response media (2) Editing the wording of the invitation It provides various setting functions such as those mentioned above. Note that the invitation text can also be edited using an existing text editor that runs on the organizer's terminal device 20. A detailed explanation of the invitation text editing function is omitted. The following describes the function for selecting the type of sending medium.

[0043] The web invitation is sent from the organizer H to the guest G as invitation information 54. Upon receiving the invitation information 54, guest G can reply to the web invitation with information such as attendance status and messages. This reply to the web invitation, including attendance status and messages, is also called reply information 55. In the following explanation, the means by which the invitation information 54 is sent to guest G is also referred to as the transmission medium. The means by which guest G sends the response information 55 in response to the invitation information 54 back to organizer H is also referred to as the reply medium.

[0044] Web invitations can be sent via email, social media, etc. Reply methods include the URL (link information or string) of the web page where the response information input screen is located, a QR code representing this URL, or social media that displays the response information input screen.

[0045] Thus, since the event management system 1 allows users to select email or social media as the medium for sending web invitations, the organizer H can send event invitations even if they do not know the official name or address of the guest G. Furthermore, the event management system 1 includes a mechanism (for example, a URL, a QR code, or integration with social media) for accessing the input screen for response information 55 in the reply medium of the web invitation. Therefore, compared to when responses are obtained from guests G in paper form, the organizer H can reduce the workload of compiling the responses.

[0046] [Photo sharing function (image upload function)] Event management system 1 has a function that allows organizer H to request guest G to share image files (IMG) that guest G possesses. Image files (IMG) include, for example, digital photographs and videos. In the following explanation, these digital photographs and videos will be collectively referred to as photographs.

[0047] In recent years, there has been a growing trend to project images such as photos and videos of the event organizer H (for example, the bride and groom at a wedding) and guests G onto screens set up at the event venue. However, there are challenges in gathering images to use for the projection, as it is time-consuming and laborious, and using only images owned by the organizer H can lead to a bias in content.

[0048] If organizer H could request guest G to provide photos that guest G possesses, it would save organizer H time and allow them to efficiently obtain a large number of photos. However, traditionally, it has been difficult for organizer H to make such a request to guest G because it was unclear when to ask guest G, or it would increase the burden on guest G.

[0049] Therefore, the event management system 1 of this embodiment includes an image upload function that reduces the effort required for guest G to provide photos, and allows organizer H to easily request guest G to provide photos they possess. The image upload function is described below. Image uploading refers to the sharing of photos, videos, and other images owned by Guest G with Organizer H and other Guest Gs. In the following explanation, the act of Guest G uploading photos to Event Management System 1 (i.e., image uploading) will also be referred to as photo sharing.

[0050] [Photo sharing settings] (Step S220) The display control unit 304 displays the photo sharing settings screen P3 on the display unit 21.

[0051] Figure 6 shows an example of the photo sharing settings screen P3 of this embodiment. The photo sharing settings screen P3 includes a photo sharing function usage setting field P31. The photo sharing function usage setting field P31 is an operation field where the organizer H sets whether or not to request guest G to share photos. If the organizer H requests photo sharing (i.e., uses the photo sharing function), they operate the button image that displays "Use".

[0052] If the organizer H performs the setting operation to use the photo sharing function, the display control unit 304 will display the guidance text editing screen P4 on the display unit 21.

[0053] Figure 7 shows an example of the guidance text editing screen P4 of this embodiment. The guidance text editing screen P4 includes a guidance text editing field P41 and a guidance text save button P42. The guidance text editing field P41 is where the organizer H edits the guidance text that is presented to guest G when requesting photo sharing from guest G. The guidance text save button P42 is an operation image for saving the guidance text displayed in the guidance text editing field P41.

[0054] The organizer terminal device 20 transmits setting information regarding whether or not to use the photo sharing function, and a message for when to use the photo sharing function, to the event management device 30 as photo sharing setting information.

[0055] Furthermore, if you are managing event guests G on a group basis, you can also configure whether or not to use the photo sharing function on a group basis.

[0056] (Step S320) When the event management device 30 receives photo sharing setting information from the organizer terminal device 20, it stores the photo sharing setting information in the storage unit 390.

[0057] [Sending invitations] (Step S230) When the organizer terminal device 20 receives the invitation sending operation from organizer H, it sends an invitation sending instruction to the event management device 30.

[0058] (Step S330) When the event management device 30 receives an instruction to send an invitation from the organizer terminal device 20, it instructs the guest terminal device 10 and the invitation printing server 40 to send the invitation. At this time, the notification unit 311 determines whether or not to request photo sharing from guest G based on the photo sharing setting information stored in step S320. For guest G who has been set to use the photo sharing function, the notification unit 311 sends a request for photo sharing along with the invitation notification to the event. In other words, the notification unit 311 can also be said to be a request unit that requests photo sharing from guest G.

[0059] As described above, the event management system 1 can manage event guests G on a group basis. For events where guests G are managed on a group basis, the event management system 1 can set whether or not to use the photo sharing function on a group basis.

[0060] In other words, the notification unit 311 (request unit) requests the event organizer H to the event guests G to upload images (IMG) related to the event, group by group.

[0061] In other words, the notification unit 311 (request unit) can choose whether or not to request photo sharing (uploading image files) for each group.

[0062] Furthermore, the event management system 1 may provide a web page that can be used by guests G belonging to the group to which paper invitations are sent. When guests G who have received a paper invitation access this web page, the web page may provide links for photo sharing and a screen for uploading photos.

[0063] Furthermore, the event management system 1 may also have a function to accept congratulatory gifts from guest G to organizer H, in conjunction with the photo sharing request. If the system is configured to accept congratulatory gifts from guest G, the event management system 1 will notify guest terminal device 30 about accepting the gifts at the same time as the photo sharing request. The "congratulatory gift acceptance (function)" referred to here means accepting congratulatory gifts via online payment before the wedding day, instead of the traditional method of accepting them in cash on the wedding day.

[0064] [How to send invitations] We will now explain the specific steps involved in sending both paper and web-based invitations.

[0065] (1) In the case of paper invitations: Paper invitations are printed by an organization using the invitation printing system 4 (for example, a printing company) and sent to guest G. In step S330, the event management system 1 sends invitation data and address data as invitation order information 53 to the invitation printing server 40 of the invitation printing system 4, as information for creating paper invitations. The invitation data includes the design data for the printed surface of the paper invitation. The address data includes the official name and address information of guest G.

[0066] If the notification unit 311 (request unit) is configured to print a reply-to code on the paper invitation, it sends the invitation order information 53, including the information needed to print the reply-to code, to the invitation printing server 40. The information needed to print the reply-to code is also called the reply-to address information. The reply-to code includes the URL string of the reply destination, a QR code representing the URL, etc. However, the reply-to code does not include the address string of the reply destination (a string that allows a human to pinpoint its location on a map; for example, the home address of organizer H).

[0067] Additionally, a photo upload destination code can be printed on the paper invitation. If the notification unit 311 (request unit) is configured to print the upload destination code on the paper invitation, it includes the information for printing the upload destination code in the invitation order information 53 and sends it to the invitation printing server 40. The information for printing the upload destination code is also called the upload destination address information. The upload destination code includes the URL string of the upload destination, a QR code representing the upload destination URL, and other similar elements.

[0068] In other words, when a paper invitation (paper media) is selected as the type of sending medium, the notification unit 311 (request unit) outputs upload destination address information, along with information about guest G, for printing an upload destination code on the paper invitation (paper media) that indicates the computer address to which the photos will be uploaded.

[0069] Furthermore, the notification unit 311 (request unit) outputs invitation order information 53 (order information), which includes information about guest G and instructions for delivering printed paper invitations (paper media) containing the event details to the event organizer.

[0070] (Step S410) The printing company receives invitation order information 53, which includes these invitation data and address data. (Step S420) The printing company generates print data based on the received invitation order information 53. The printing company prints and sends paper invitations based on the generated print data.

[0071] At this time, the recipient of the paper invitations is predetermined by the organizer H. Specifically, it is set whether the printed paper invitations are sent to organizer H in a batch (for example, by mail or courier) or sent to each guest G individually. By setting the invitations to be sent to organizer H, organizer H can check the finished product of the paper invitations before they are sent to guests G. On the other hand, by setting the invitations to be sent directly to guests G, organizer H can avoid the trouble of mailing the paper invitations. In this case, organizer H can also select the type of stamp (stamp design) to be attached to the paper invitations. The information on the recipient of the paper invitations and the stamp selection information when direct delivery to guests G is selected are included in the invitation order information 53.

[0072] The paper invitation has an upload destination code printed on it, which indicates the computer address where you can upload your photos.

[0073] In other words, the notification document regarding the event invitation will include a link that directs the user to the registration screen.

[0074] In this example, the invitation printing system 4 is described as being used by an organization separate from the organization using the event management system 1 (for example, a printing company). However, this is not limited to this; the invitation printing system 4 may also be used by the organization using the event management system 1 (or related organizations such as subsidiaries or affiliates) as an integral part of the event management system 1. In other words, the organization using the event management system 1 may use the invitation printing system 4 to print paper invitations.

[0075] (2) In the case of a web invitation: On the other hand, in step S330, the web invitation is sent from the event management device 30 to the guest terminal device 10 used by each guest G. At this time, the web invitation is sent (for example, directly) without going through a system that creates paper invitations, such as the invitation printing system 4. As described above, the event management device 30 stores a guest list in its storage unit 390, which includes information about the recipients of guest G, such as their email addresses and SNS addresses. The event management system 1 sends invitation information 54 to the guest terminal device 10 based on the destination information for guest G included in this guest list.

[0076] Additionally, the web invitation can display the photo upload destination code. The notification unit 311 (request unit) sends the invitation information 54 to the guest terminal device 10, which includes information for displaying the upload destination code, to the guest G who has been set to use the photo sharing function. The event management system 1 may also have a function to copy the photo upload destination code to the storage unit (e.g., clipboard) of the organizer terminal device 20. In this case, the organizer H does not send the photo upload destination code to the guest terminal device 10 using the functions provided by the event management system 1 (e.g., directly), but rather sends the photo upload destination code to the guest terminal device 10 using the information communication functions of the organizer terminal device 20 (e.g., email or SNS messenger, etc.) (e.g., indirectly).

[0077] [Event attendance confirmation and photo sharing operations] (Step S110) The receiving unit 131 of the guest terminal device 10 receives the invitation information 54. Upon receiving the invitation information 54, the guest terminal device 10 displays an image based on the invitation information 54 (i.e., a web invitation) on the display unit 11. As described above, the web invitation includes access information to the input screen for response information 55 using the response medium set by the organizer H (e.g., URL, QR code, SNS account, etc.).

[0078] Figure 8 shows an example of the invitation screen P101 of this embodiment. The invitation screen P101 includes an attendance button P1011, a guest type button P1012, and a name input field P1013. The attendance button P1011 is an operation image that accepts the guest G's response regarding attendance at the event. The guest type button P1012 is an operation image that sets the type of guest G (for example, whether they are a guest from the groom's side or a guest from the bride's side). The name input field P1013 is a field for entering the guest G's name.

[0079] Once the guest G has finished entering information in each field of the invitation screen P101, the guest terminal device 10 displays the photo sharing request screen P102 on the display unit 11.

[0080] Figure 9 shows an example of the photo sharing request screen P102 of this embodiment. The photo sharing request screen P102 includes a message field P1021, an upload field P1022, a name input field P1023, an upload button P1024, and a hold button P1025.

[0081] The photo sharing request screen P102 can also be described as a reception screen for accepting photo uploads.

[0082] In other words, the display control unit 304 displays a reception screen to the guest G of the event, which accepts the upload of an image IMG related to the event from the guest G. Based on a selection operation on a part of the reception screen, the display control unit 304 displays an image IMG selection screen to select the image IMG to be uploaded. In other words, the display control unit 304 functions as a reception screen display control unit and a selection screen display control unit.

[0083] The announcement text field P1021 is where the announcement text entered by the organizer H in the announcement text editing field P41 (see Figure 7) is displayed.

[0084] The upload field P1022 is where guest G selects and registers the image (IMG) to be uploaded from among the photos it owns. By performing an operation to select the designated area in the upload field P1022 (for example, by tapping or clicking), the guest terminal device 10 is redirected to the image storage screen. Guest G then selects and specifies the image (IMG) to be uploaded from the redirected screen, preparing the photo for upload. Note that multiple photos can be registered at once in the upload field P1022.

[0085] The upload button P1024 is an operation image that accepts the operation to upload the photo file pasted in the upload field P1022 to the event management device 30. If multiple photos are registered in the upload field P1022, operating the upload button P1024 will send all registered photos to the event management device 30 at once.

[0086] The Hold button P1025 is an operation image that accepts the action of holding off on uploading photos. Holding off on uploading means that when the organizer H has requested photo sharing, guest G does not upload the photos, or decides to upload the photos at a later date.

[0087] The photo sharing request screen P102 (i.e., the reception screen) is displayed chronologically immediately after the invitation screen P101, that is, the notification screen regarding the event invitation.

[0088] In other words, the registration screen is displayed immediately after the notification screen regarding the invitation to the event. With the event management system 1 configured in this way, users can upload photos to share at the same time as they respond to the event's attendance confirmation. If the system has a function to accept congratulatory gifts, the following screens will be displayed in order: invitation screen P101, congratulatory gift acceptance screen (not shown), and photo sharing request screen P102. In this case, the photo sharing request screen P102 (i.e., the acceptance screen) can be said to be displayed chronologically consecutively after the notification screen regarding the event invitation. That is, "displayed chronologically consecutively" includes cases where no other screens are displayed between the invitation screen P101 and the photo sharing request screen P102, and cases where other screens (for example, the congratulatory gift acceptance screen) are displayed between the invitation screen P101 and the photo sharing request screen P102.

[0089] Furthermore, the event management system 1 can set a deadline for guests G to respond to event invitations. In this case, the event management system 1 may also allow setting a separate deadline for uploading photos. For example, even if the attendance response deadline is set more than one month before the event date, the photo upload deadline can be set from one month before the event date to the day of the event.

[0090] The deadline for responding to an event invitation is sometimes set well in advance of the event date, due to factors such as venue reservations. For example, if the event is a wedding, the organizer H might reserve the venue six months to a year before the event date (i.e., the wedding day) and finalize the number of guests G one to two months before the event. On the other hand, even if photos are uploaded shortly before the event (for example, from one month before to the day of the event), it may still be possible to use the uploaded photos in the event's presentation. In this case, if the deadline for uploading photos and the deadline for responding to attendance responses can only be set on the same day, the period for uploading photos will be relatively short, which may result in insufficient photo collection.

[0091] According to the event management system 1, which allows for separate settings of the photo upload deadline and the attendance response deadline, the photo upload deadline can be set just before the event date, increasing the number of photos that can be collected from guests G.

[0092] (Step S120) The guest terminal device 10 transmits the data of the attendance response to the event and the photos to be uploaded entered by guest G to the event management device 30 as response information 55. Specifically, the attendance response transmission unit 132 transmits the attendance response to the event invitation. The image upload control unit 133 uploads the photos.

[0093] As described above, the event management system 1 of this embodiment can upload multiple photos at once.

[0094] In other words, the image upload control unit 133 can upload multiple image IMGs selected by the guest G on the image IMG selection screen all at once.

[0095] If the photo upload is pending, the image upload control unit 133 will not upload the photo. On the other hand, even if the photo upload is pending, the attendance response transmission unit 132 will send an attendance response to the event invitation. In this case, the image upload control unit 133 uploads the photo when the hold on the photo upload is released (i.e., when guest G performs an upload operation).

[0096] In other words, the attendance response transmission unit 132 transmits the attendance response to the event invitation. The image upload control unit 133 uploads the image (IMG) after the attendance response has been submitted.

[0097] (Step S330) The reply receiving unit 321 of the event management device 30 receives the reply information 55 sent by the guest terminal device 10. The attendance information acquisition unit 322 acquires the attendance information of guest G included in the response information 55 and stores it in the storage unit 390.

[0098] If the response information 55 contains data for the photo to be uploaded, the image upload reception unit 331 retrieves the photo data contained in the response information 55. The image storage unit 332 stores the photo data retrieved by the image upload reception unit 331 in the storage unit 390.

[0099] As described above, the event management system 1 of this embodiment can manage guests G by group (community). The image storage unit 332 can sort and save the photos to be uploaded that are sent from guests G according to the group to which the guest G belongs.

[0100] In other words, the image storage unit 332 stores the image IMGs uploaded by guest G based on the request, group by group.

[0101] [Viewing uploaded photos] (Step S240) The organizer's terminal device 20 displays the browsing screen P5.

[0102] Figure 10 shows an example of the viewing screen P5 of this embodiment. The viewing screen P5 includes an attendance column P51 and a photo viewing button P52. The attendance column P51 is a column that displays attendance responses based on the response information 55 stored in the event management device 30. The attendance column P51 displays the total number of people attending the event and the total number of people absent. The photo viewing button P52 is an operation image used when viewing photos. When the organizer H operates the photo viewing button P52, the organizer terminal device 20 displays the photo viewing screen P6 on the display unit 21.

[0103] Figure 11 shows an example of the photo viewing screen P6 of this embodiment. The photo viewing screen P6 includes a photo display area P61 and a reminder button P62. The photo display area P61 is a field where multiple photos (images IMG) uploaded by guest G are displayed. The photo display area P61 may have a function that allows multiple photos to be selected at once from the multiple photos displayed, which can then be used for the event's presentation. For example, the organizer H may have a function that allows them to download the selected photos to the organizer terminal device 20 all at once, or to automatically put the selected photos into a folder and send it via email or the like. In this case, the folder containing the multiple photos may be automatically compressed. When creating videos, etc., using photos collected from guests, it is conceivable that the work may be outsourced to a third party, so making it easy to send the collected images increases convenience.

[0104] In this way, the organizer H can use the organizer terminal device 20 to view multiple photos stored in the storage unit 390 of the event management device 30 all at once.

[0105] In other words, the notification unit 311 notifies the event organizer H of the event guest G of the request to upload an image IMG related to the event, along with the invitation to the event. The image upload reception unit 331 can accept the upload of multiple image files (IMG) at once. The image storage unit 332 saves the received image IMGs in a way that allows them to be displayed in a list.

[0106] In other words, the event management system 1 functions as an image acquisition system. The event management system 1 may also be referred to as the image acquisition system.

[0107] With the event management system 1 configured in this way, guest G can upload multiple photos at once, coinciding with the timing of their attendance response to the event invitation. The event management system 1 allows guest G to upload photos without any confusion about when and to what recipient to upload them. Furthermore, with the event management system 1, guest G does not need to upload photos one by one. Because the event management system 1 configured in this way reduces the effort required of guest G, organizer H can easily collect photos that guest G possesses from guest G.

[0108] [Reminder for Guest G to upload images] The reminder button P62 is an interactive image that accepts the operation to remind guest G to upload an image.

[0109] (Step S250) When the reminder button P62 is pressed, the organizer terminal device 20 displays the reminder operation screen P7 on the display unit 21.

[0110] Figure 12 shows an example of the reminder operation screen P7 of this embodiment. The reminder operation screen P7 includes a reminder target selection field P71. The reminder target selection field P71 is a screen that pops up on the photo viewing screen P6 described above. The reminder target selection field P71 includes a link acquisition button P711.

[0111] The link acquisition button P711 is an operation image used to obtain the address information of the photo upload destination. When the organizer H operates the link acquisition button P711, the address information of the photo upload destination is copied to a temporary storage area (e.g., the clipboard) in the organizer's terminal device 20. The photo upload destination address information includes the URL string of the upload destination, image data of a two-dimensional code representing the upload destination URL, etc.

[0112] Organizer H can send the copied address information to guest G via communication functions such as email or social networking services.

[0113] Please note that the URL for uploading photos will be prepared individually for each event and for each group of guest G. For example, there are three link acquisition buttons: P711-1 for the first group (e.g., family and relatives), P711-2 for the second group (e.g., schoolmates and friends), and P711-3 for the third group (e.g., colleagues). With the event management system 1 configured in this way, the organizer H can easily obtain a URL prepared individually for each group of guests G and notify the guests G.

[0114] Furthermore, the event management system 1 may have a function to notify multiple guests G belonging to a group of group URLs obtained by the organizer H.

[0115] (Step S130) The guest terminal device 10 notifies guest G that the organizer H has sent a reminder about sharing photos. This notification includes the address information for the photo upload destination. Guest G can use the photo upload destination address information included in the notification to upload their own photos.

[0116] [Reminder via email to guest G] In addition to the actions of organizer H described above, reminders to guest G may also be sent by the event management system 1 without any action from organizer H (i.e., automatically) if certain conditions are met.

[0117] The event management system 1 automatically sends various notifications to guest G at various times (automatic notifications) as configured in advance by the organizer H. Examples of automatic notifications include notifications prompting guests to respond to event attendance confirmations, notifications confirming receipt of contact from guest G to organizer H, and alert notifications informing guests that the date of the ceremony is approaching. The notification unit 311 adds a photo upload reminder to the content of these automatic notifications and sends them to guest G.

[0118] The notification unit 311 provides a reminder by including information indicating where to upload the photos (for example, a web address such as a URL, or an email or social media address to which the organizer H has an account) in the text of various notifications. For example, when guest G responds to an attendance response, the notification unit 311 sends a notification (e.g., a registration completion email) to guest G who has responded that they will attend, indicating that their attendance registration is complete. In this example, a reminder for photo sharing is sent to guest G who has responded that they will attend, but among guest G who has responded that they will not attend, there may be some who have given up attending due to unavoidable circumstances but would still like to cooperate by providing photos. Therefore, the system may be designed to also send a reminder to guests who have responded that they will not attend.

[0119] Figure 13 shows an example of the text P103 of the registration completion email in this embodiment. The text P103 of the registration completion email includes a link to accept congratulatory gifts P1031 and a photo sharing link P1032.

[0120] Event management system 1 has a function to accept congratulatory gifts from guests G who will be attending (or not attending) an event (for example, a wedding or its after-party) via online payment on a website.

[0121] The congratulatory gift acceptance link P1031 is a field containing the URL of the page for accepting congratulatory gifts via online payment, or its hyperlink. The URL for the online congratulatory gift acceptance page is prepared individually for each event. Event Management System 1 presents the URL of the congratulatory gift acceptance page, which is prepared individually for each event, in the text of the registration completion email P103.

[0122] The photo sharing link P1032 is a field containing the address information for where the photos will be uploaded (for example, the URL of the upload destination). As mentioned above, the URL for uploading photos is prepared individually for each event and for each group of guest G.

[0123] Event management system 1 is, for example, • Send an invitation to Guest G for the event. • Notification prompting guest G to respond regarding their attendance at the event. • Confirmation of receipt of contact from guest G to organizer H It has a function to request photo sharing from guest G at various times, such as these.

[0124] In other words, the notification unit 311 notifies guest G of the upload request by including information indicating the upload destination for the image IMG in at least one of the following: a notification inviting guest G to the event, a notification prompting guest G to respond regarding attendance at the event, and a notification confirming receipt of contact from guest G to organizer H.

[0125] In other words, the notification unit 311 can request the upload of an image IMG at at least two timings: a first timing corresponding to the timing of the notification of the event invitation to guest G, and any second timing after the first timing. The first timing refers to the timing of the event invitation notification (for example, the timing of step S230 described above). The second timing refers to the timing after the notification of the event invitation (for example, the timing of step S250 mentioned above).

[0126] The event management system 1 can request photo uploads at multiple timings, such as the first and second timings, thereby increasing the number of photos that can be collected from guest G.

[0127] The second timing can be any time after the first timing, for example, immediately after the first timing (for example, at a different time on the same day as the event invitation notification, or the day after the event invitation notification).

[0128] [Upload images at any time] Guest G can upload photos at any time after being invited to an event. Guest G can also upload photos regardless of whether they attend or not.

[0129] (Step S140) Guest G uploads photos by operating the guest terminal device 10. Specifically, when Guest G activates the photo upload function, the guest terminal device 10 displays the photo sharing request screen P102 (see Figure 9) on the display unit 11. Guest G uploads photos to the event management device 30 by operating each field on the photo sharing request screen P102.

[0130] (Step S340) The image upload reception unit 331 of the event management device 30 accepts image uploads from the guest terminal device 10. The image storage unit 332 saves the uploaded photos to the storage unit 390.

[0131] (Step S260) The organizer terminal device 20 displays the browsing screen P5 in the same manner as in step S240.

[0132] In other words, the image upload reception unit 331 accepts image uploads (IMG) at any time and without limit on the number of uploads after an upload request has been made. Some guests G may realize they have images (IMG) to share after responding to the invitation. The event management system 1 of this embodiment can accept image uploads (IMG) at any time and without limit on the number of uploads. With the event management system 1 configured in this way, the organizer H can collect more photos from guests G.

[0133] [Viewing shared photos among guests] Furthermore, the event management system 1 may have a function that allows other guests G to view photos uploaded by guest G. In this case, when guest G uploads a photo, the system may have a function that allows them to choose whether or not to grant viewing permission to other guests G, in addition to granting viewing permission to organizer H. Furthermore, when guest G uploads a photo, if organizer H grants permission to view the uploaded photo, the system may also have a function to grant restricted viewing permission to other guests G.

[0134] Furthermore, the system may have a function that allows Guest G to grant permission for the use of photos according to their intended purpose. For example, Guest G might decide that a photo is suitable for use in a video shown on the day of the event, but not for inclusion in a booklet distributed on the day of the event. In such cases, the event management system 1 can make it easier for Guest G to provide photos and collect more photos from Guest G by allowing them to set permission for use according to the purpose of the photo.

[0135] [Upload images from the event day] Furthermore, the event management system 1 may also have a function to accept photo uploads from guests G on the day of the event. For example, the event management system 1 issues a URL for uploading photos on the day of the event. This URL for uploading photos on the day of the event (or a QR code to access this URL, etc.) can be displayed on a bulletin board or video projection screen at the event venue on the day of the event. The event management system 1 may have a function to save photos uploaded to the upload URL on the day of the event, and a function to edit photos into a slideshow digest.

[0136] According to the event management system 1 configured in this way, it is possible to collect photos from guests G who were invited via paper invitation and were unable to upload their photos in advance via the web, as well as from guests G who forgot to upload their photos. Furthermore, according to the event management system 1, photos taken on the day of the event can be uploaded, allowing event participants to view numerous photos taken from various angles immediately after the event ends, which has the effect of increasing guest satisfaction with the event. In addition, photos taken on the day of the event can be displayed at the event venue or included in thank-you notes distributed at a later date.

[0137] Furthermore, the event management system 1 can also link the completed guest information to other systems (for example, a seating arrangement system or a system for ordering items such as wedding favors) for subsequent tasks such as creating seating charts.

[0138] As described above, according to the event management system 1 of this embodiment, the organizer H can easily collect images owned by guest G from guest G.

[0139] Although embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like are also included within the scope of the gist of the present invention. For example, a computer program to implement the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here may include hardware such as an operating system and peripheral devices.

[0140] Furthermore, "computer-readable recording media" refers to writable non-volatile memory such as flexible disks, magneto-optical disks, ROMs, and flash memory, portable media such as DVDs (Digital Versatile Discs), and storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording media" also includes volatile memory (such as DRAM (Dynamic Random Access Memory)) within computer systems that act as servers or clients when programs are transmitted via networks such as the Internet or communication lines such as telephone lines, which retain programs for a certain period of time.

[0141] Furthermore, the above program may be transmitted from a computer system that stores the program in a memory device or the like to another computer system via a transmission medium or by transmission waves within the transmission medium. Here, the "transmission medium" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like a telephone line. Furthermore, the above program may be intended to implement only a portion of the functions described above. It may also be a so-called differential file (differential program) that can implement the aforementioned functions in combination with programs already recorded in the computer system. [Explanation of Symbols]

[0142] 1…Event management system, 10…Guest terminal device, 11…Display unit, 12…Operation unit, 13…Calculation unit, 14…Storage unit, 20…Organizer terminal device, 21…Display unit, 22…Operation unit, 23…Calculation unit, 24…Storage unit, 30…Event management device, 300…Calculation unit, 390…Storage unit

Claims

1. For events where the event organizer manages the guests of the event in groups, The event organizer requests that each group of guests upload images related to the event, and A storage unit that stores images uploaded by guests based on requests, for each of the aforementioned groups, An image acquisition system equipped with the following features.

2. The request unit can request the upload of the image at at least two timings: a first timing corresponding to the timing of notifying the guest of the event invitation, and any second timing after the first timing. The image acquisition system according to claim 1.

3. The request unit can select whether or not to request the upload of the image for each group. The image acquisition system according to claim 1.

4. On the computer, For events where the event organizer manages the guests of the event in groups, The event organizers will request each group of guests to upload images related to the event. The images uploaded by guests based on the request will be saved for each of the aforementioned groups, A program to execute.

Images