Photo studio management method, management device, and management system

Abstract

To enable users to be confident that image data of consistent quality is to be provided.SOLUTION: In the method for managing photo studios, reservation information including photographing details at one of selected photo studios and contact information of a user is received from a user terminal operated by the user and recorded (S1502). When image data obtained by photographing according to the photographing details is received from a store terminal provided in the photo studio that referred to the photographing details, the image data is recorded in association with the reservation information (S1506). The recorded image data is then provided using the contact information of the user included in the reservation information (S1508).SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] The present invention relates to a photo studio management method, a management device, and a management system. [Background technology]

[0002] The delivery format and quality of the photographs taken often differ depending on the photographer or photo studio, and it can be important to decide which photographer or photo studio to commission. Patent Document 1 relates to a technology for commissioning a photography company to take photographs at an event venue, and discloses a matching support system that matches users with photography companies. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-310617 Summary of the Invention [Problem to be solved by the invention]

[0004] When the subject is a human, the quality of the photograph is important, especially when taking profile pictures to be posted on a website or ID photos to be attached to resumes sent to employers, so there is still a high demand for photography in photo studios.

[0005] On the other hand, since the long travel time to a photo studio is a burden for the person being photographed, the person often requests the photo to be taken at a photo studio in their own living area, i.e., their place of residence, workplace, or school. In recent years, moreover, electronic image data is sometimes provided to the user without the delivery of printed photographs.

[0006] However, because there are various methods for communicating shooting conditions to photo studios and various formats for delivered image data, the quality of the finished image data, such as its format, is not uniform, making it difficult for users to be confident that the delivered image data will exceed a certain level of quality.

[0007] The present invention has been made in consideration of such problems, and aims to provide a photo studio management method, management device, and management system that can give users confidence that image data of a certain quality will be provided. [Means for solving the problem]

[0008] The photo studio management method of the present invention is a method for managing multiple photo studios. In this management method, reservation information including the content of photography at one of the selected photo studios and the user's contact information is received and recorded from a user terminal operated by the user, and image data obtained by photography corresponding to the content of photography is received from a store terminal installed in the photo studio that referenced the content of photography. The image data and the reservation information are recorded in association with each other, and the recorded image data is provided using the user's contact information included in the reservation information.

[0009] The photo studio management device of the present invention is a management device for multiple photo studios. This management device includes a reservation information receiving unit that receives and records reservation information, including the content of photography at one of the selected photo studios and the user's contact information, from a user terminal operated by the user, an image data receiving unit that receives image data obtained by photography corresponding to the content of photography from a store terminal installed in the photo studio that referenced the content of photography and records the image data in association with the reservation information, and an image data providing unit that provides the recorded image data using the user's contact information included in the reservation information.

[0010] The photo studio management system of the present invention is a management system that includes a management device that manages multiple photo studios, a user terminal operated by a user, and a store terminal installed in the photo studio. The management device receives and records reservation information from the user terminal, including the content of the photo shoot at one of the selected photo studios and the user's contact information, and when it receives image data obtained by shooting according to the content of the photo shoot from the store terminal that references the content of the photo shoot, it records the image data in association with the reservation information, and provides the recorded image data using the user's contact information included in the reservation information. [Effects of the Invention]

[0011] According to the photo studio management device, management method, and management system of the present invention, even if multiple photo studios are operated, reservation information including the content of the shoot and the user's contact information is recorded, image data of the photos taken based on the content of the shoot is created, the image data is recorded in association with the reservation information, and the recorded image data is provided to the user's terminal using the contact information included in the reservation information. Therefore, regardless of which of multiple studios the photo shoot is conducted at, the entire process from reservation, photography, and delivery can be carried out in one stop, allowing users to have confidence that image data of a certain quality will be provided. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a schematic configuration diagram of a photo studio management system according to a first embodiment. [Figure 2] FIG. 10 is a flowchart showing a reservation process. [Figure 3] FIG. 2 is a diagram illustrating an example of a reservation database. [Figure 4] FIG. 10 is a flowchart showing processing during photography. [Figure 5] FIG. 10 is a diagram illustrating an example of an additional information database. [Figure 6] FIG. 2 is a diagram illustrating an example of a photography information database. [Figure 7]5 is a diagram showing an example of a display screen of a store terminal in the photographing process of FIG. 4. FIG. [Figure 8] FIG. 10 is a flowchart illustrating a delivery process. [Figure 9A] FIG. 10 is a diagram showing an example of a login screen when providing delivery image data. [Figure 9B] FIG. 10 is a diagram illustrating an example of a download page. [Figure 9C] FIG. 10 is a diagram showing an example of a download page in which photographed data is available for download. [Figure 9D] FIG. 10 is a diagram showing an example of a download page after an image display operation unit is operated. [Figure 9E] FIG. 10 is a diagram showing an example of a display screen after a consent operation by a consent operation unit. [Figure 9F] FIG. 10 is a diagram showing another example of the display screen before the consent operation by the consent operation unit. [Figure 10] FIG. 10 is a diagram illustrating an example of a delivery information database. [Figure 11] 10 is a flowchart showing a re-shooting / refund process. [Figure 12] FIG. 10 is a diagram illustrating an example of a reshoot / refund database. [Figure 13] FIG. 10 is a flowchart illustrating a user introduction process. [Figure 14] FIG. 10 is a diagram illustrating an example of a referral management database. [Figure 15] FIG. 10 is a flowchart of another example of the first embodiment. [Figure 16] FIG. 10 is a schematic configuration diagram of a photo studio management system according to a second embodiment. [Figure 17] FIG. 10 is a flowchart showing an initial setting process for group photography reservation. [Figure 18] FIG. 10 is a diagram illustrating an example of a photography group database. [Figure 19] FIG. 10 is a diagram illustrating an example of a group special notes database. [Figure 20] FIG. 10 is a diagram illustrating an example of a reservation form information database. [Figure 21]FIG. 10 is a diagram illustrating an example of a store confirmation information database. [Figure 22] FIG. 2 is a diagram illustrating an example of a photography information database. [Figure 23] FIG. 10 is a flowchart showing management control of members. [Figure 24] FIG. 10 is a diagram illustrating an example of a member list database. [Figure 25] FIG. 10 is a flowchart illustrating another example of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below with reference to the accompanying drawings. In the following description, the same components are designated by the same reference numerals, and redundant description will be omitted.

[0014] (First embodiment) 1 is a schematic diagram of a photo studio management system 1 according to the first embodiment. The management system 1 includes a management device 2, a head office terminal 3, a user terminal 4, and two store terminals 5 installed in stores A and B. The management device 2, the head office terminal 3, the user terminal 4, and the two store terminals 5 are configured to be able to communicate with each other via a network.

[0015] The management device 2 is a device that controls the entire management system 1. The management device 2 transmits and receives data between the head office terminal 3, the user terminal 4, and the store terminal 5, and performs various processes such as photo shooting reservations, uploading photo data, and delivering photo data.

[0016] The head office terminal 3 can acquire information about photography at each store from the management system 1, and performs processing as needed for customers at each store in response to operations by the operator of the head office terminal 3. For example, the head office terminal 3 can handle complaints from customers, and specifically, can cause the management system 1 to process requests such as refunding the photography fee to the customer who made the complaint or instructing them to take the photo again.

[0017] The user terminal 4 is a terminal operated by the user who will be photographed, and in most cases is a smartphone owned by the user. The user's terminal 4 accesses the management system 1 in response to the user's operation, specifies a date and time, and reserves a photo shoot at any store. When making a reservation, a photo shoot plan (for example, resume, passport, promotional photo, etc.) is specified. After the photo shoot is completed, the user is provided with the photographed photo data via the user terminal 4.

[0018] The store terminal 5 is a terminal located in each photo studio. By accessing the management device 2, the store terminal 5 can obtain reservation details, upload photographed photo data, and provide the uploaded photo data to the user terminal 4.

[0019] The head office terminal 3, the user terminal 4, and the store terminal 5 perform operations in response to operations by the operator of each terminal. In the following, for the sake of readability, descriptions of the operations of the operators will be omitted, and operations will be described as being performed by the head office terminal 3, the user terminal 4, and the store terminal 5 mainly accessing the management device 2. Furthermore, the screens displayed on the head office terminal 3, the user terminal 4, and the store terminal 5 are generated by the management device 2. In the following, for the sake of readability, descriptions will be described as being performed by the management device 2 mainly displaying a predetermined screen on the display screen of another terminal.

[0020] The management device 2, head office terminal 3, user terminal 4, and store terminal 5 may be general computers or servers, and these devices may be equipped with a control unit consisting of a CPU (Central Processing Unit) or GPU (Graphics Processing Unit) that controls the entire device, a recording unit consisting of ROM (Read Only Memory), RAM (Random Access Memory), and / or a hard disk, etc., that records programs and various data, etc., a communication unit that communicates with the outside, a display unit that displays data on an information display device such as a touch panel, and an input unit that accepts input from devices such as a touch panel.

[0021] The control unit, recording unit, communication unit, display unit, and input unit are configured to be able to communicate with each other. The management device 2, head office terminal 3, user terminal 4, and store terminal 5 are configured to be able to perform predetermined processes by executing programs recorded in the recording units. The hardware configurations of the management device 2, head office terminal 3, user terminal 4, and store terminal 5 are merely examples, and it is sufficient that they are configured to be able to perform predetermined processes by running the recorded programs.

[0022] 2 is a flowchart showing the reservation process. By accessing the management device 2 with the user terminal 4, the user makes a reservation for photography at a certain store.

[0023] In step S201, the user terminal 4 accesses the reservation screen provided by the management device 2 and starts a reservation operation.

[0024] In step S202, the management device 2 displays a selection screen for photography shops (photo studios) on the display unit of the user terminal 4. In step S203, the user terminal 4 accesses the selection screen for photography shops provided by the management device 2, selects one shop desired by the user, and transmits information about the reserved shop to the management device 2.

[0025] In step S204, when the management device 2 receives the information about the selected reservation store, it displays a selection screen for selecting available photo shoot dates and times at the selected store on the display unit of the user terminal 4. In step S205, the user terminal 4 accesses the selection screen for photo shoot dates and times provided by the management device 2, selects the date and time desired by the user, and transmits information about the reservation date and time to the management device 2.

[0026] In step S206, when the management device 2 receives the selected reservation date and time, it displays a selection screen for photo shoot plans available for reservation at the selected store on the display unit of the user terminal 4. In step S207, the user terminal 4 accesses the selection screen for photo shoot plans provided by the management device 2, selects the photo shoot plan desired by the user, and transmits information on the selected photo shoot plan to the management device 2.

[0027] In step S208, when the management device 2 receives the selected photography plan, it displays an input screen for contact information such as the user's name, email address, and telephone number on the display unit of the user terminal 4. In step S209, the user terminal 4 inputs the user's contact information via the contact information input screen displayed by the management device 2 and transmits the contact information to the management device 2.

[0028] In step S210, the management device 2 displays a screen on the display unit of the user terminal 4 to prompt the user to confirm the reservation information based on the information received in steps S203 to S209. In step S211, when the user terminal 4 confirms the reservation information displayed in step S210, it transmits a confirmation to the management device 2.

[0029] In step S212, when the management device 2 receives confirmation of the reservation information from the user terminal 4, it registers the confirmed reservation details in the reservation database (DB) 300. In step S213, the management device 2 notifies the user terminal 4 of the reservation details registered in step S212 by means of displaying on a web page, sending an email, or the like.

[0030] 3 is a diagram showing an example of the reservation database 300 recorded in step S212. Note that the reservation database 300 shown in the figure is just an example, and some of the items shown in the figure may be missing, or other items may be included.

[0031] As shown in this figure, the reservation database 300 has a user ID (identifier) ​​301 and a kana name record column 302, as well as an email address record column 303, a telephone number record column 304, a reservation date and time record column 305, a reservation store record column 306, a photography plan record column 307, a memo record column 308, and a registration date and time record column 309, all of which correspond to the user ID (identifier) ​​301 and kana name record column 302.

[0032] 2 are recorded in the user ID record column 301 and the registration date and time record column 309. The reservation store record column 306 records the information received in step S203, the reservation date and time record column 305 records the information received in step S205, and the photography plan record column 307 records the information received in step S207. The kana name record column 302, email address record column 303, and phone number record column 304 record the user information received in step S209. The memo record column 308 records special notes from the head office terminal 3 or the store terminal 5 as necessary. Note that the memo record column 308 may also record link information that allows reference to materials stored in the management device 2.

[0033] The photography plan record column 307 records the purpose (job hunting, passport, job change), as well as whether makeup needs to be applied by staff at the store, whether the photographed data needs to be edited, the print size, etc. The content recorded in the photography plan record column 307 is based on the user's input in step S207.

[0034] Figure 4 is a diagram showing a flowchart illustrating the processing performed when photography is performed in a store. In the following, the image data captured as is will be referred to as "photography data," one piece of the photography data selected and modified as necessary will be referred to as "basic image data," and the basic image data resized to the delivery size will be referred to as "delivery image data." These types of image data are sometimes referred to collectively as image data, photography data, and photo data without distinction.

[0035] In step S401, the store terminal 5 accesses the management device 2 to refer to the reservation database 300. By referring to the photography plan record column 307 in the reservation database 300, the store staff can check not only the purpose of the photo, but also whether makeup or retouching is required, and delivery information, and make preparations before the photo shoot.

[0036] In step S402, the user terminal 4 operated by the visiting user transmits the additional information to the management device 2 via a screen displayed on the display unit of the user terminal 4, which is generated by the management device 2. In step S403, upon receiving the additional information input in step S402, the management device 2 updates the additional information database 500.

[0037] 5 is a diagram showing an example of additional information database 500. In additional information database 500, information is provided in kanji name record column 501 and address record column 502 in correspondence with user ID record column 301 and kana name record column 302. Furthermore, if a questionnaire is conducted upon visit to the store, the results of the questionnaire may be recorded in questionnaire result record columns 503 and 504. This information is referenced by management device 2 and store terminal 5 as necessary.

[0038] 4 again, in step S404, the store terminal 5 transmits the photographing information according to the user's input to the management device 2 via a screen generated by the management device 2 and displayed on the display unit. In step S405, upon receiving the photographing information input in step S404, the management device 2 updates the photographing information database 600.

[0039] 6 is a diagram showing an example of a photography information database 600. The photography information database 600 has a camera in charge record column 601, a makeup artist in charge record column 602, and an image data registration status record column 603, which correspond to the user ID record column 301 and kana name record column 302. The camera in charge record column 601 and the makeup artist in charge record column 602 record the person in charge of photography and makeup. The image data registration status record column 603 also records the registration status of the image data. When the delivery image data is uploaded to the management device 2 (step S415), the registration status record column 603 is changed from "unregistered" to "registered."

[0040] 4 again, in step S406, after the makeup artist applies makeup to the user who is being photographed and the photographer takes a photograph, the store terminal 5 creates photographic data by copying the photographic data from the camera or the like used for the photograph. Note that the store terminal 5 may also create photographic data in a predetermined format by, for example, automatically executing image processing software from the photographic equipment. Then, in step S407, the store terminal 5 uploads all of the photographic data to the management device 2.

[0041] In step S408, the management device 2 registers all of the photographic data received in step S406. In this case, the management device 2 may determine whether the subject of the received image data is the same as the user. If the management device 2 determines that they are the same, it records the received image data, and if it determines that they are not the same, it discards the received image data and notifies the store terminal 5 that they are not the same.

[0042] For example, a photo may be registered in which the subject holds a board indicating the user's ID and name during pre-photography, as in the registered image data 752 shown at the bottom of Fig. 7. In such a case, the management device 2 reads the user's ID and name and determines whether the read information matches the user's ID and name, thereby determining whether the subject in the basic image data is the same as the user. Other information, such as gender and age, may also be used to determine whether the subject and the user are the same.

[0043] In step S409, the store terminal 5 determines basic image data from all the photographed data. For example, the basic image data is the basis for the delivery data, and is determined by the user selecting one from all the photographed data. Furthermore, if the photographed image needs to be corrected, the correction processing is also performed based on the user's instructions, and the basic image data is generated.

[0044] In step S410, in response to an operation by a store staff member, the store terminal 5 uploads the basic image data to the management device 2. Then, in step S411, the management device 2 records the basic image data accepted in step S410. In this case, the management device 2 may determine whether the accepted basic image data meets predetermined shooting conditions and format. If the management device 2 determines that the shooting conditions and format are met, it records the accepted basic image data; if it does not determine that the conditions are not met, it discards the accepted basic image data and notifies the store terminal 5 that the conditions are not met.

[0045] For example, the management device 2 determines that the predetermined photographing conditions are not met if, for example, the photograph is for identification purposes but is taken sideways rather than frontally, or if the teeth are showing. If a different background color is used despite a background color being specified, the management device 2 determines that the photographing conditions are not met. The format (size and file format) of the basic image data may be based on a standard specified in the photography plan recording field 307 (FIG. 3), and the management device 2 may determine whether or not the standard is met. Additionally, the management device 2 may further determine whether the subject of the photographed data recorded in step S408 is the same as the subject of the basic image data uploaded in step S410.

[0046] In step S412, the store terminal 5 accesses the management device 2 to specify the delivery size. Here, the delivery size is the size of the image data to be delivered, and is set as a default value according to the photography plan record field 307 of the reservation database 300. In response to a request from the user, the delivery size may be changed by operation from the store terminal 5, or another delivery size may be specified.

[0047] In step S413, the management device 2 determines the delivery size in accordance with the operation in step S412. In step S412, if a predetermined size is specified from the store terminal 5, the predetermined size is used as the delivery size, and if not specified, the default value, i.e., the size shown in the photography plan record field 307, is used as the delivery size.

[0048] In step S414, the store terminal 5 creates delivery image data according to the delivery size determined in step S413. In step S415, the store terminal 5 uploads the delivery image data created in step S414.

[0049] In step S416, the management device 2 determines whether the delivery image data accepted in step S410 meets the delivery size determined in step S411, and if it determines that it meets the delivery size, it registers the uploaded delivery image data. Similar to checking the size of the delivery image data, the management device 2 may further determine whether the subject of the accepted delivery image data is the same as the user, and whether predetermined shooting conditions are met.

[0050] 7 is a diagram showing an example of the display screen of the store terminal 5 during the photographing process of FIG. 4. Photographed data in which the user is the subject, basic image data, and delivery image data are uploaded via this display screen. The delivery image data is then ultimately provided to the user terminal 4.

[0051] The name display section 701 at the top of the screen indicates that delivery work will be carried out for Mr. Xyama Xo, whose user ID is 001, and also shows the photography plan record field 307 (Fig. 3). The user change section 702 allows the user ID to be entered and the user ID to be associated with the image data to be uploaded can be selected.

[0052] The delivery format display section 703 indicates whether all the photographic data will be delivered to the user in addition to the delivery image data corresponding to a specified shot. Specifically, a display according to the contents of the all data delivery necessity record field 1001 recorded in the delivery information database 1000 in FIG. 10 described below is displayed. Note that by operating the delivery format display section 703, it is possible to selectively change whether all the photographic data will be delivered. If not all the photographic data will be delivered, the image data uploaded in response to operations in the first shot display area 721 and, if necessary, the second shot display area 731 will be delivered. If all the photographic data will be delivered, all the photographic data uploaded in the all photographic data display area 751 will also be delivered.

[0053] In response to an operation, the delivery processing operation unit 704 instructs the management device 2 to provide the delivery data to the user terminal 4. When a delivery processing request is made to the management device 2 in response to an operation of the delivery processing operation unit 704 (S801 in FIG. 8), a download page for the delivery data is provided to the user terminal 4 (S803). In addition, the upper part of the delivery processing operation unit 704 shows the date and time when the delivery processing was performed (if it has been performed multiple times, the most recent date and time), and the delivery status can be checked from the head office terminal 3 or the store terminal 5.

[0054] An image data registration section 705 is shown below the name display section 701, user change section 702, delivery format display section 703, and delivery processing operation section 704. The image data registration section 705 includes a photographer display area 711, a first cut display area 721, a second cut display area 731, a cut addition area 741, and a total shooting data display area 751.

[0055] The photographer display area 711 is a display area for the photographer who took the photo. The item name "Photographer who took the photo" is displayed in the left column, and the photographer selection section 712 is displayed in the right column. By operating the photographer selection section 712 (the area labeled "Select" in the illustrated example), the photographer selected from the list can be input and recorded.

[0056] The first cut display area 721 is an area for registering delivery data of a predetermined size (cut 1). The items in the left column of the first cut display area 721 show a size change operation section 722 and an addition operation section 723. After operating the size change operation section 722 to specify a size, a cut of the specified size can be added below (for example, as the second cut display area 731) by operating the addition operation section 723.

[0057] The right column of the first cut display area 721 is an area where image data is registered and displayed. In this example, photographed data is registered in four areas, registration areas 724 to 727, which are arranged side by side in the horizontal direction. In the registration areas 724 to 727, "basic image (image A) a.jpg," "original print image (s.jpg)," "reduced image (ss.jpg)," and "print image (ssi.jpg)" are registered, respectively. In addition, an addition area 728 is provided below the registration areas 724 to 727, and by operating the addition area 728, new image data can be registered.

[0058] Referring to the registration area 724 in detail, a thumbnail display section 724A showing a thumbnail image of the registered image data is displayed in the center, and above that are an image name display section 724B and a registrable size display section 724C. The image name display section 724B shows "Basic image (image A) a.jpg" as the type of photographic data to be registered, and the registrable size display section 724C shows the size of the image data that can be registered, "4160px wide, 6240px high."

[0059] Also, below the reduced display section 724A, a select button 724D is displayed on the left and a delete button 724E is displayed on the right. By operating the select button 724D, image data stored in the store terminal 5 is uploaded to the management device 2, and a reduced image of the uploaded image data is displayed in the reduced display section 724A. By operating the delete button 724E, the registered image data can be deleted.

[0060] Further below the select button 724D and the delete button 724E, an information display section 724F is provided. The file name and size of the registered image data are displayed in the information display section 724F. A non-display operation section 724G is provided below the information display section 724F. By operating the non-display operation section 724G, it is possible to change whether or not to deliver the image data registered in the registration area 724 (whether or not to display it on the delivery screen). In the illustrated example, the non-display operation section 724G is a checkbox, and when checked, it is hidden (not delivered), and when unchecked, it is displayed (delivered).

[0061] The same displays as 724A to 724G in registration area 724 are also displayed in registration areas 725 to 727. Note that the size of the captured data that can be registered is displayed in the registrable size display area (no symbols are attached for readability) of registration areas 725 to 727. For example, the size display area of ​​registration area 725 states "900px or more in width, 1200px or more in height," and image data that meets this standard can be registered.

[0062] The second cut display area 731 has the same configuration as the first cut display area 721, but the items in the left column are different. In addition to a resizing operation section 732, the left column also shows a cut before resizing display section 733 and a delete operation section 734. The second cut display area 731 is essentially created by resizing the cut indicated in the cut before resizing display section 733 (in this figure, cut 1 shown in the first cut display area 721), but the base cut can be changed by operating the cut before resizing display section 733. The entire second cut display area 731 can be deleted by operating the delete operation section 734.

[0063] A cut display area can also be added by operating the "+" section in the right column of the cut addition area 741.

[0064] The all image data display area 751 is a work area for registering image data. The left column indicates that this is the area where all image data is uploaded, and that the format of the uploaded image data must be "jpg."

[0065] The right column shows multiple registration areas, similar to the first cut display area 721 and second cut display area 731. Although no symbols are provided for readability, photographic data can be registered in these areas by operating the registration button and selection button. As shown in registered image data 752, photographic data showing the subject holding a board indicating the user ID and name before shooting may be uploaded for user ID verification.

[0066] 7 is generated by the management device 2 and displayed on the display unit of the store terminal 5. The store staff can upload the photographed data to the management device 2 by operating the registration screen on the store terminal 5.

[0067] FIG. 8 is a flowchart of the delivery process.

[0068] In step S801, the store terminal 5 requests the management device 2 to perform delivery processing by specifying a customer ID, and makes the management device 2 ready to provide the delivery image data registered in the management device 2 to the user terminal 4. For example, the request for delivery processing to the management device 2 may be made by operating the delivery processing operation unit 704 in Fig. 7, or may be made in response to another operation.

[0069] In step S802, the management device 2 creates a download page for the delivery image data in response to the delivery processing request, and also creates the user's login information (user ID and corresponding password). This information is transmitted in the subsequent step S803, so the delivery date and time to the management device 2 is recorded. The recorded transmission date and time is used for display at the top of the delivery processing operation unit 704, etc.

[0070] In step S803, the management device 2 transmits the URL of the download page and login information to the email address associated with the user ID.

[0071] In step S804, the user terminal 4 uses the information received in step S803 to access the download page of the management device 2. In step S805, the management device 2 creates a login screen for the download page and displays it on the user terminal 4. In step S806, the user terminal 4 enters the login information transmitted in step S803 into the login screen, thereby gaining access to the download page.

[0072] 9A is a diagram showing an example of a login screen when providing delivery data. A customer name corresponding to a user ID is displayed in a name display area 911. The user enters the user ID and password notified in step S804 into a reception number input field 912 and a password input field 913, and operates a login operation unit 914, allowing the user terminal 4 to access the download page.

[0073] Referring back to FIG. 8, in step S807, the management device 2 creates a download page in response to the login information entered in step S806, and displays it on the user terminal 4.

[0074] 9B is a diagram showing an example of a download page. The user ID and the corresponding user name are displayed in a name display area 911. Below the name display area 911, a first warning display area 921, a thumbnail image display area 922, a second warning display area 923, an agreement operation area 924, and a download history display area 925 are displayed.

[0075] The first warning display area 921 is an area showing how to use the download page. The thumbnail image display area 922 is an area showing a thumbnail image of the user's image. The second warning display area 923 is an area showing how to use the download page, just like the first warning display area 921. In this example, it shows the download deadline and that re-shooting after downloading and refund guarantees are not applicable. The thumbnail image display area 922 displays a thumbnail of one of the delivery data.

[0076] The consent operation section 924 is displayed in correspondence with the second warning display area 923, and accepts an operation indicating consent to the content displayed in the second warning display area 923. In the illustrated example, the consent operation section 924 is a checkbox, and when it is unchecked, consent is not given, and when it becomes checked in response to a user operation, consent is given.

[0077] The download history display section 925 shows the download history of the photographed data that has been downloaded using the user ID in the past. The download history display section 925 shows, for example, the access history, such as the number of accesses, the download date and time, the IP address of the access source, the browser, and the device (OS).

[0078] Referring again to FIG. 8, in step S808, the user terminal 4 operates the consent operation section 924 on the download page (FIG. 9B) to transmit to the management device 2 that the user agrees to the download conditions.

[0079] In step S809, the management device 2 creates a download page in which the delivery image data can be downloaded in response to the consent input in step S808, and displays the page on the user terminal 4.

[0080] 9C is a diagram showing an example of a download page in which delivery image data is available for download. In addition to a name display area 911, a first warning display area 921, a thumbnail image display area 922, a second warning display area 923, a consent operation area 924, and a download history display area 925, a first image display operation area 931, a second image display operation area 932, and a third image display operation area 933 are also shown. In the example shown, the checkbox in the consent operation area 924 is checked. Then, by operating the first image display operation area 931, the second image display operation area 932, and the third image display operation area 933, the delivery image can be displayed and downloaded.

[0081] 8 again, in step S810, the user terminal 4 operates the first image display operation section 931 to the third image display operation section 933 on the download page (FIG. 9C). As a result, the delivery image data is displayed on the user terminal 4, and the image data becomes available for download.

[0082] 9D is a diagram showing an example of a download page after operating the first image display operation unit 931 to the third image display operation unit 933. When the first image display operation unit 931 to the third image display operation unit 933 are operated, the third warning display area 941 is again displayed, indicating that the image is not eligible for re-shooting or refund guarantee after download. Then, after operating the agreement operation unit 942, the delivered image data may be displayed and made available for download. When the disagreement operation unit 943 is operated, the delivered image data is not displayed.

[0083] 9E is a diagram showing an example of a display screen after the consent operation by the consent operation unit 942. As shown in the figure, the delivery image data is displayed in the image display area 951. The user terminal 4 can download the delivery image data displayed in the image display area 951.

[0084] 9F is an example of a display screen before the consent operation by consent operation unit 942. According to this figure, before the consent operation, the word "sample" is displayed in the image data as in sample display area 961. For example, an operation unit for displaying a sample screen in third warning display area 941 in FIG. 9D may be provided, and the image of FIG. 9F may be displayed in response to operation of that operation unit. As another example, the screen of FIG. 9F may be displayed after operation of first image display operation unit 931 to third image display operation unit 933 in FIG. 9C, and then the screens of FIGS. 9D and 9E may be displayed.

[0085] 10 is a diagram showing an example of the delivery information database 1000. The delivery information database 1000 can be referenced and recorded in various situations including delivery processing.

[0086] The delivery information database 1000 includes, for example, a column 1001 for recording whether all data needs to be delivered, a column 1002 for recording whether data needs to be sent, a column 1003 for recording whether data needs to be sent, a column 1004 for recording whether download status is required, and a column 1005 for recording delivery status, in correspondence with the user ID column 301 and the kana name column 302.

[0087] The all data delivery necessity record field 1001 is referenced when displaying the delivery form display section 703 in Fig. 7, and records whether all photographed data needs to be delivered. The data transmission necessity record field 1002 records whether data transmission is necessary, and in principle, "data transmission" is recorded as necessary. For example, if only printed photographs are provided and data transmission is not necessary, "not necessary" is recorded.

[0088] 8 is performed, and the date and time when the download page and login information are transmitted to the user terminal 4 is recorded in the data transmission status record field 1003. The recorded information in the data transmission status record field 1003 is displayed above the delivery processing operation section 704 on the screen in FIG. 7. Note that multiple transmission histories can be registered in a table (not shown), and the most recent transmission history among these may be displayed in the data transmission status record field 1003.

[0089] 8 is performed and the delivery image data is displayed in a downloadable state after the consent operation section 924 is operated, the date and time of the processing is recorded in the download status record field 1004. If the image is displayed multiple times, all display histories may be recorded in a table (not shown). All recorded display histories are displayed in the download history display section 925 of FIGS. 9B to 9F.

[0090] The delivery status is recorded in the delivery status record field 1005, and when the user terminal 4 performs the consent operation and the delivery image data is displayed in a downloadable state, the status of "delivered" is recorded. This delivery status can be used to manage the delivery status.

[0091] 11 is a flowchart showing the re-photographing / refund process. In this diagram, the re-photographing process is shown in steps S1101 to S1106, and the refund process is shown in steps S1111 to S1113. In this diagram, the terminal operated by the person who is to have the photo re-photographed is shown as user terminal 4A, and the terminal operated by the person who is to have the refund shown as user terminal 4B.

[0092] First, the re-photographing process will be described. In step S1101, when the store terminal 5 receives a request for re-photographing from a user, it designates the user ID to the management device 2 and requests the management device 2 to transmit a re-photographing guide to the user.

[0093] 12 is a diagram showing an example of the re-photographing / refund database 1200. The re-photographing / refund database 1200 has a re-photographing acceptance information record column 1201, a re-photographing reason record column 1202, a refund acceptance information record column 1203, a refund reason record column 1204, and a latest download status record column 1205, which correspond to the user ID record column 301 and kana name record column 302. The re-photographing acceptance information record column 1201, the re-photographing reason record column 1202, the refund acceptance information record column 1203, and the refund reason record column 1204 are updated by operations from the head office terminal 3 or the store terminal 5. The latest download status record column 1205 records the same information as the latest download status record column 1004 of the delivery information database 1000.

[0094] 11 again, before requesting the transmission of the re-photographing information in step S1101, the store terminal 5 may check whether the delivery image data has been downloaded by referring to the latest download status record column 1205 of the re-photographing / refund database 1200. In addition, the staff member operating the store terminal 5 may confirm the reason for the refund with the user, and may record the confirmed reason for the refund in the re-photographing reason record column 1202 of the re-photographing / refund database 1200.

[0095] In step S1102, the management device 2 updates the re-photography acceptance information record column 1201 of the re-photography / refund database 1200 in response to the request to send a re-photography invitation from the store terminal 5 in step S1101. In step S1103, the management device 2 sends a re-reservation invitation to the contact information for the user ID specified in the request to send a re-photography invitation. The re-reservation invitation includes a reservation URL. In step S1104, the user terminal 4 can make a reservation for a re-photography by accessing the reservation URL included in the re-reservation invitation received in step S1103. In step S1105, the management device 2 updates the reservation date and time record column 305 and reservation store record column 306 of the reservation database 300 and the re-photography acceptance information record column 1201 of the re-photography / refund database 1200 based on the re-reservation details accepted in step S1104. In step S1106, the management device 2 sends the re-reservation details to the user terminal 4.

[0096] In this way, reservations made via the reservation URL provided by the management device 2 as a re-reservation are recorded in the memo record column 308 etc. of the reservation database 300 so that a discount or no charge can be applied.

[0097] Next, the refund process will be described. In step S1111, when the store terminal 5 accepts a request for re-photographing from a user, it specifies the user ID to the management device 2 and requests the management device 2 to process a refund for that user. The store terminal 5 may check whether the delivery image data has been downloaded by referring to the latest download status record column 1205 of the re-photographing / refund database 1200. In addition, the staff member may confirm the reason for the refund with the user, and may record the confirmed reason for the refund in the refund reason record column 1204 of the re-photographing / refund database 1200.

[0098] In step S1112, the management device 2 performs a predetermined refund process in response to the refund process request from the store terminal 5 in step S1111, and updates the refund acceptance information record field 1203 in the re-photographing / refund database 1200. The refund process can be performed by any method, such as bank transfer or cancellation of credit card usage.

[0099] In step S1113, the management device 2 transmits a message indicating that the refund process has been completed to the user terminal 4 associated with the user ID specified in the request to transmit the re-photographing information. If the refund is to be made by bank transfer and the user's account number is unknown, the account number may be inquired in this step.

[0100] Figure 13 is a flowchart of the user introduction process. When a user finishes taking photos and is notified of the download page for the delivered image data and login information, a referral URL is also sent along with that information. Once a user has finished taking photos, they can introduce their photo shoot to other users by sending the referral URL.

[0101] In Figure 13, the introducing side is shown as user terminal 4C, and the introduced side is shown as user terminal 4D. Also, since the processing in Figure 13 corresponds to one or more of the processing described so far, the corresponding processing is shown in parentheses for reference. The corresponding processing steps written in parentheses are added to help understand the correspondence, and do not indicate a strict correspondence.

[0102] 8, the store terminal 5 requests delivery processing by specifying a customer ID to the management device 2. The processing of step S1301 corresponds to step S801 in FIG.

[0103] Step S1302 corresponds to step S802, and the management device 2 creates a download page for the captured image data and the user's login information (user ID and corresponding password), and records the transmission date and time. Note that the processing in step S1302 corresponds to step S802 in FIG.

[0104] Step S1303 corresponds to step S803, and the management device 2 transmits the URL of the download page and login information to the email address associated with the user ID to the user terminal 4C. In addition to this information, when introducing photography to another user (introduced person), an introduction URL used for making a reservation for the introduced person is transferred to the user terminal 4C. After this, as in steps S804 to S810, the user terminal 4C acquires the delivery image data, but the acquisition process is not shown. The process of step S1303 corresponds to step S803 in FIG. 8.

[0105] In step S1304, the introducer's user terminal 4A transmits the introduction URL received in step S1303 to the introduced user terminal 4B.

[0106] In step S1305, the user terminal 4B accesses the management device 2 using the introduction URL received in step S1304 to reserve the photo shoot. Then, in step S1306, the management device 2 updates the reservation database 300, and in step S1307, the management device 2 transmits the confirmed reservation details to the introduced user terminal 4B. Note that the processes of steps S1305 and S1306 correspond to steps S201 to S212 in Figure 2, and the process of step S1307 corresponds to S213. Furthermore, in step S1305, the management device 2 updates the introduction management database 1400, which will be described later.

[0107] In step S1308, the store terminal 5 creates the photographed data, and then in step S1309 uploads various image data such as the photographed data and delivery image data. The processes in steps S1308 and S1309 correspond to steps S401 to S416 in FIG.

[0108] In step S1310, the store terminal 5 instructs the management device 2 to perform delivery work. In step S1311, the management device 2 creates a download page and the user's login information (user ID and corresponding password), sends this information to the user terminal 4A, and records the date and time of transmission. In step S1312, the management device 2 sends the URL of the download page and the login information to the email address associated with the user ID of the introduced user terminal 4B. Here, in the introduction process, an introduction URL that encourages the user to introduce the photography to other users is also sent to the user terminal 4A. Here, the processes of steps S1310 to S1312 correspond to steps S801 to S803, respectively.

[0109] Thereafter, in step S1313, the user terminal 4D accesses the download page of the management device 2, and in step S1314, the management device 2 creates a login screen for the download page and displays it on the display unit of the user terminal 4D. Here, the processing in steps S1313 to S1314 corresponds to steps S804 to S809.

[0110] Furthermore, in step S1314, when the management device 2 displays the downloadable delivery image data, it refers to the referral management database 1400 to identify the user ID of the introducer of the user ID of the referee. Then, in step S1315, the management device 2 transmits a referral benefit to the user terminal 4A associated with the introducer's user ID. The referral benefit may be points that can be used in exchange for money at various stores, not just photo studios.

[0111] 14 is a diagram showing an example of a referral management database 1400. The referral management database 1400 may be recorded in conjunction with the reservation database 300, or may be managed as an integrated database. The referral management database 1400 has a user ID record field 1401, an email address record field 1402, an introducer ID record field 1403, a registration date and time record field 1404, a photography date and time record field 1405, a referral status record field 1406, a number of reservations record field 1407, a number of photos taken record field 1408, and a referral URL record field 1409, and this information is used in the referral process of FIG.

[0112] The user ID recording field 1401 records identification information assigned to each user, which may be the same as the user ID recording field 301 in the reservation database 300 or the like, or may store identification information assigned separately for referral management. The email address recording field 1402 records the same information as the email address recording field 303 used in the reservation database 300 or the like.

[0113] In the introducer ID recording field 1403, if the user is an introducer, the user ID of the introducer (introducer) is recorded. That is, if a user (introduced person) makes a reservation using an introduction URL sent from the introducer (introducer) (step S1305), the user ID of the introducer to whom the introduction URL was distributed is recorded. For example, in the illustrated example, user ID: 102 is an introducer, and the introducer is the user with user ID: 101.

[0114] The date and time when the reservation process of steps S201 to S213 was performed if the user was not an introduction, or the date and time when the reservation process of steps S1305 to S1307 was performed if the user was an introduction, is recorded in the registration date and time recording field 1404. The date and time when the reservation process of steps S401 to S406 was performed if the user was not an introduction, or the date and time when the reservation process of steps S1308 to S1309 was performed if the user was an introduction, is recorded in the photography date and time recording field 1405.

[0115] In the referral status record column 1406, when the user in the user ID record column 1401 is making a reservation through an introduction, the reservation process of steps S1305 to S1307 is performed, and "reserved" is recorded when the reservation of the introduced person (the user in the user ID record column 1401) is completed. After that, when the delivery work of steps S1313 and S1314 is completed, "completed" is recorded. When the status becomes "completed," a referral benefit is sent to the introducer (step S1315).

[0116] The number of reservations recorded in the reservation count field 1407 is the number of introduced people who have made reservations through a referral by the user with the user ID, and the number of photos taken recorded in the photo count field 1408 is the number of introduced people who have actually completed downloading the delivery photo data. The reservation count field 1407 and the photo count field 1408 can be used to manage the referral process.

[0117] The referral URL record field 1409 records the URL of a reservation page where a reservation can be made by specifying an introducer, and when a reservation is accepted from the reservation page of this URL, the referral management database 1400 is updated. The URL recorded in the referral URL record field 1409 is sent to the user terminal 4 when the delivery photography data is delivered in steps S1303 and S1312, and is forwarded by the user to the introduced person (S1403), and is used when the introduced person makes a reservation (S1305). Using this referral management database 1400, the referral process shown in FIG. 13 is performed.

[0118] (Variation) The following describes modifications in which the first embodiment described with reference to FIGS. 1 to 14 is realized in other ways.

[0119] 15 is a flowchart showing the processing of the management system 1 in the modified example. In this figure, it is assumed that a photo shoot reservation is made on the user terminal 4D operated by the introduced person using the introduction URL provided by the user terminal 4C operated by the introducer.

[0120] In step S1501, the user terminal 4D accesses the management device 2 using an introduction URL such as that shown in the introduction URL record field 1409, selects one of multiple stores, and makes a reservation. In this process, reservation information and introduction information are sent to the management device 2. Note that the reservation information includes items contained in each item in the reservation database 300, but may also include not only the date and time of photography at a certain store and the user's contact information, but also the photography conditions requested by the user and delivery standards for the photo data to be delivered. For example, the delivery standards may be determined based on information such as that in the photography plan record field 307. The introduction information may be any information that can identify the referral source, as in the introduction URL record field 1409, and may take any format, such as inputting an introduction code.

[0121] In step S1502, the management device 2 accepts the reservation information accepted in step S1502 and updates the reservation database 300 to record the reservation information. In addition, the management device 2 identifies and records the introducer by referring to the introduction management database 1400 using the accepted introduction information.

[0122] In step S1503, before starting photography at the store, the store terminal 5 accesses the management device 2 and references the photography conditions and delivery standards included in the reservation information. In step S1504, once photography is performed based on the photography conditions, the store terminal 5 creates photo data in a format according to the reservation conditions. Thereafter, in step S1505, the store terminal 5 uploads the created photo data to the management device 2.

[0123] In step S1506, the management device 2 determines whether the photo data received in step S1503 meets the delivery criteria. As one example, the management device 2 determines whether the photo data meets the format (file format and size) requirements determined according to the photography plan record column 307 of the reservation database 300. As another example, the management device 2 may determine whether the owner and the subject are the same based on a character string obtained from image data such as the registered image data 752 in FIG. 7, or estimated values ​​of gender and age. As yet another example, the management device 2 may use previously registered photo data to determine the quality of the photo and determine whether the delivery criteria are met.

[0124] In step S1507, the management device 2 creates a download page to be used to provide the photo data to the user, along with the corresponding login information. Then, in step S1508, the management device 2 transmits the download page and the corresponding login information to the user terminal 4D. The download page may include a past download history, such as the download history display section 925.

[0125] The provision of photo data is not limited to the format of entering a user ID and password on a download page (Figure 9A), but may also be sent as an attachment to an email after consent to the conditions for obtaining image data, which will be described later, has been obtained. It is preferable to provide the user's photo data to the user after explicitly receiving consent from the user to obtain image data, and various methods of providing the data are possible.

[0126] In step S1509, the user terminal 4D accesses the download page notified in step S1507 using the login information, and performs consent processing to the conditions for providing image data via the consent operation unit 924. Thereafter, in step S1510, the management device 2 displays the photo data (FIG. 9E), and in step S1511, the user terminal 4D downloads the displayed photo data.

[0127] 9C and 9D, when a consent operation is performed by the consent operation unit 924, the management device 2 records the consent history, and may display the consent history in the download history display unit 925 on the download page. Note that the operation recorded as the history is not limited to the consent operation, but may be any operation, such as displaying image data, that can be regarded as the user agreeing to the conditions for providing image data.

[0128] Also, in step S1510, if the management device 2 confirms that the photo shoot reservation made by the user terminal 4D that has agreed to the acquisition of image data includes referral information and is made by the person being introduced, it may send a referral benefit to the user terminal 4C operated by the introducer.

[0129] Note that the management device 2 may have a control unit provided with a plurality of functionally different blocks that perform the above-described processes. That is, the management device 2 may have functional blocks such as a reservation information receiving unit that receives and records reservation information from the user terminal 4, an image data receiving unit that receives and records image data transmitted from the store terminal 5, and an image data providing unit that provides the recorded image data.

[0130] In the method for managing multiple photo studios in the first embodiment, reservation information including the photo shoot content at one selected from multiple photo studios and the user's contact information is accepted and recorded from the user terminal 4D (S1501, S1502). The photo shoot content in the reservation information is referenced from the store terminal 5 of that photo studio, and a photo is taken. Then, when the photo data of the photo is accepted from the store terminal 5, the photo data is recorded in association with the reservation information (S1506). Thereafter, the recorded photo data is provided using the user's contact information included in the reservation information (S1507-S1511).

[0131] In this process, when photography is taken at multiple stores, image data is generated according to the reservation details, and the registered photography data is provided using the contact information included in the reservation information. Therefore, since the reservation process and the creation and provision of the photography data are performed in conjunction with each other, it is easy to standardize photography reservations at multiple stores and the format of the photography data provided to users. As a result, regardless of which of multiple stores is used, the entire process from reservation, photography, and delivery is performed in one stop, allowing users to be confident that image data of a consistent quality will be provided.

[0132] According to the method for managing multiple photo studios of the first embodiment, delivery standards are set according to the content of the photo shoot, and are determined based on, for example, the purpose corresponding to the photo shoot plan record field 307 and the size indicated in the registerable size display area 724C corresponding to the photo shoot plan record field 307. Then, it is determined whether the photo data to be registered meets the delivery standards, and if the photo data meets the delivery standards, the photo data is registered. This makes it easy to standardize the format of the photo data provided to users, further enabling users to have confidence that image data of a certain quality will be provided.

[0133] According to the method for managing multiple photo studios of the first embodiment, the delivery criteria may be related to the identity of the subject shown in the photo data and the user. For example, the identity of the subject and the user may be determined using photo data, such as registered image data 752, in which the subject holds a board indicating the user's ID and name during a pre-photography session. Alternatively, the identity may be determined using the user's gender and age, which may be included in the reservation information. This reduces the likelihood of errors in the photo data provided to the user, further enabling the user to have confidence that image data of a certain quality will be provided.

[0134] According to the method for managing multiple photo studios of the first embodiment, when downloading image data, the image data can be acquired after consenting to the image data acquisition conditions from the user terminal 4D. Then, when image data is provided to the user terminal 4 again after the consent operation, this history can be displayed on the display unit of the user terminal 4. In this way, it becomes clear that consenting to the image data acquisition conditions has been explicitly recorded, and therefore agreement regarding the provision conditions between the image data provider and the image data recipient is made clear, allowing for highly transparent transactions.

[0135] According to the method for managing multiple photo studios of the first embodiment, when the recorded photo data is provided, referral information to be used for introducing photography to other users is included. After the photo data is provided to the introduced person, the referral benefit is provided by contacting the contact information included in the reservation information of the user who made the introduction. In this way, the referral information that the user can use for introducing photography can be provided at the time of delivery, thereby increasing the number of photo shoots at the photo studio.

[0136] (Second embodiment) In the first embodiment, a case where a user takes a photo individually is described. In the second embodiment, a case where a photo is taken of members (users) belonging to a certain group as the subjects is described. For example, the group may be an entertainment agency or a company, and the members of the group, such as the talents and employees, are the subjects. These users can make reservations and take photos at different stores.

[0137] FIG. 16 is a schematic configuration diagram of a management system 1 of the second embodiment. Compared to the management system 1 of the first embodiment (FIG. 1), the management system 1 of the second embodiment further includes a client terminal 6. The client terminal 6 is an example of a group management terminal. In this embodiment, the user terminal 4 is an example of a member terminal.

[0138] The client terminal 6 is a terminal operated by an administrator (for example, a staff member in the management department) of the entire group to which the user belongs. The client terminal 6 accesses the management device 2 to manage the photography of the users of the entire group.

[0139] 17 is a flowchart showing the initial setting process for group photography reservations. This flowchart involves a management device 2 that manages the entire system, a head office terminal 3 that manages the photography store, a client terminal 6 operated by the group manager, and a user terminal 4 operated by the group members. Furthermore, as a preliminary step to this process, it is assumed that a contract for photography for the group members is concluded between the company that manages the photography store and the group to which the photography members belong.

[0140] In step S1701, the head office terminal 3 requests group registration from the management device 2. In step S1702, the management device 2 creates a photography group database 1800 in the management device 2 in response to the group registration request in step S1701.

[0141] 18 is a diagram showing an example of a photography group database 1800. The photography group database 1800 has a group ID record column 1801, a group name record column 1802, a group details record column 1803, an in-house person in charge record column 1804, a client person in charge name record column 1805, a client email address record column 1806, an access restriction IP address record column 1807, and a reservation URL record column 1808.

[0142] The group ID recording field 1801 records identification information for each group that is automatically assigned by the management system 1. The group name recording field 1802 records a name used to indicate a shooting group. In the example of this figure, group IDs: 001 and 002 record groups of talent agencies whose members are affiliated talents, and group ID: 003 records a group of companies whose members are employees.

[0143] The groups managed in the photography group database 1800 are used for convenience in relation to photography and may not be related to actual organizations. In the example of this figure, the groups with recorded information "001" and "002" in the group ID recording field 1801 are for photographing talents belonging to the same entertainment company, and although the photographed persons overlap, different groups are set depending on the photography method.

[0144] A detailed description of the group is entered arbitrarily in the group details record field 1803. The name of the person in charge who operates the head office terminal 3 is recorded in the in-house person in charge record field 1804. The name, telephone number, and email address of the administrator of the group who operates the client terminal 6 are recorded in the client person in charge name record field 1805 and the client email address record field 1806, respectively.

[0145] The IP addresses that are permitted to access the group photo management screen via the Internet are registered in the access restriction IP address recording field 1807. The management screen can be accessed from the client terminal 6 using the user ID and password of the group administrator, but security can be made more robust by setting accessible IP addresses. Note that access to the management screen can be restricted not only by IP address but also by two-step authentication or various other methods.

[0146] The URL of a dedicated reservation page set for each group is recorded in the reservation URL recording field 1808. By having members of a group make reservations using the same URL, it becomes easier to share shooting conditions and the like.

[0147] 17 again, in step S1703, the management device 2 transmits access information including the URL and login information of the group management page to the client terminal 6. In step S1704, the client terminal 6 is able to access the management page using the received access information. Then, in step S1705, the management device 2 confirms that the connection is from an IP address recorded in the access restriction IP address record field 1807 in addition to authenticating the connection using the access information, and allows the connection.

[0148] Thereafter, in step S1706, the client terminal 6 accesses the group management page, and in addition to obtaining the URL recorded in the reservation URL recording field 1808 of the photography group database 1800, inputs data into the group special notes database 1900, the reservation form information database 2000, the store confirmation information database 2100, and the photography information database 2200. Details of these databases will be described later.

[0149] Thereafter, in step S1707, the management device 2 notifies the user terminal 4 operated by the member belonging to the group of the URL recorded in the acquired reservation URL record field 1808. In the photography group database 1800, a reservation page dedicated to the group can be accessed via the reservation URL record field 1808, but it is also possible to allow each member to access the reservation page dedicated to the group using a common login ID and password, etc. In such a case, the login ID and password are recorded as access information in the photography group database 1800 instead of the reservation URL record field 1808. Below, the various databases input in step S1707 will be described.

[0150] 19 is a diagram showing an example of a group special notes database 1900. Photo shoot reservations for group members are made based on the information recorded in the group special notes database 1900. In the group special notes database 1900, a note record column 1901, a photo shoot purpose record column 1902, a reservation-accepting store record column 1903, and a reservation CC address record column 1904 are recorded in correspondence with the group ID record column 1801 and the group name record column 1802.

[0151] The note recording field 1901 records a character string that can be arbitrarily displayed on the reservation screen when a group member makes a reservation for photography from the user terminal 4 operated by the group member. By referring to the contents of the note recording field 1901 when making a reservation, the appropriate reservation details can be entered.

[0152] The purpose of the photograph to be taken is recorded in the photographing purpose record field 1902. The information in the photographing purpose record field 1902 may be referenced not only by the user terminal 4 but also by the store terminal 5, and is used as reference information when taking a photograph.

[0153] The available reservation store record field 1903 records stores that are available for group members to make reservations. Group members can make reservations for photo shoots at stores recorded in the available reservation store record field 1903, but are restricted from making reservations at other stores. While there are differences in the quality of photographs taken at each photo studio, for example, if the same staff work at multiple stores located close to each other, the quality of photographs taken at those stores is often similar. Furthermore, if the stores do not have the same equipment, the quality of photographs taken at stores that have similar equipment will be more similar. By setting the available reservation store record field 1903 in advance based on the photography techniques and equipment of each store, the quality of the final photo data can be made closer.

[0154] In the reservation CC address record column 1904, an address that is automatically sent as a CC (Carbon Copy) when a member makes a photoshoot reservation, for example, the email address of the operator of the client terminal 6, is recorded.

[0155] 20 is a diagram showing a reservation form information database 2000. Photographing reservations for group members are made based on the information recorded in the reservation form information database 2000. In the reservation form information database 2000, corresponding to the group ID record field 1801 and the group name record field 1802, there are recorded an email address restricted domain record field 2001, a phone number restricted record field 2002, a reservation available period record field 2003, a photographing available period record field 2004, an ID number display necessity record field 2005, an ID number replacement character record field 2006, and an employee number regular expression record field 2007.

[0156] The domain of the email address that is permitted to be input when making a reservation is recorded in the email address restricted domain recording field 2001, and the telephone number that is permitted to be input when making a reservation is recorded in the phone number restricted recording field 2002. The reservation available period recording field 2003 records the period during which photography reservations are possible, and the photography available period recording field 2004 records the period during which photography is possible at the photo studio.

[0157] The ID number display necessity record field 2005 records information indicating whether or not to prompt for the input of an ID number within a group when making a reservation. Since the ID number itself differs depending on the group (for example, a talent number or an employee number), a number to prompt for input is displayed on the reservation screen based on the information recorded in the ID number replacement character record field 2006. The employee number regular expression record field 2007 records the format allowed for the ID number to be input, and only ID numbers that conform to this format are allowed to be input when making a reservation.

[0158] 21 is a diagram showing an example of a store confirmation information database 2100. The information recorded in the store confirmation information database 2100 is referenced by the store terminal 5 when photographing members. In the store confirmation information database 2100, corresponding to the group ID recording column 1801 and the group name recording column 1802, there are provided a data provision necessity record column 2101 for the person to be photographed, a data delivery necessity record column 2102, a costume change necessity record column 2103, a store approval necessity record column 2104, a billing unit price record column 2105, a file name rule record column 2106, and a cut information record column 2107.

[0159] The field 2101 for recording whether or not data is to be provided to the photographed person records information on whether or not photo data is to be delivered to the photographed person's members. For example, if the photo data only needs to be sent to the client terminal 6 and does not need to be provided to the photographed person, it is recorded as "no delivery required." The field 2102 for recording whether or not all data is to be delivered is a delivery form, and similar to the field 1001 for recording whether or not all data is to be delivered in the delivery information database 1000, information on whether or not all photographed data is to be delivered is recorded.

[0160] The costume change necessity record column 2103 and the store payment necessity record column 2104 record whether rental costumes are required for the person to be photographed when taking photos at the store and whether payment is required by the person to be photographed, and these are referenced by the store terminal 5 when taking photos. The store payment necessity record column 2104 also records whether payment for photography is required for each member at the store, and the billing unit price record column 2105 records the price per photography session. If the payment necessity record column 2104 is not required, the billing amount calculated by multiplying the amount in the billing unit price record column 2105 by the number of people to be photographed is issued directly to the client terminal 6. This reduces the workload for accounting processing.

[0161] The file name rule record field 2106 records the character string that is added to the beginning of the file name at the time of delivery. The cut information record field 2107 displays cut information that indicates the size of the delivery data referenced by the store terminal 5.

[0162] 22 is a diagram showing an example of a photography information database 2200. The photography information database 2200 is referenced by the store terminal 5 when photography is performed. The photography information database 2200 has a background color record field 2201, a smiling / unsmiling record field 2202, a teeth showing record field 2203, a looking at the camera record field 2204, a face direction record field 2205, a correction required / unnecessary record field 2206, a data format record field 2207, a size format record field 2208, a resolution record field 2209, a sample record field 2210, and a specification details record field 2211, in correspondence with the group ID record field 1801 and the group name record field 1802.

[0163] These pieces of information are referenced by the store terminal 5 and used when photographing the person to be photographed during store photography. Specifically, the background color at the time of photography is recorded in the background color recording field 2201. The smiling / unsmiling / unclearing recording field 2202, the teeth showing / unclearing recording field 2203, and the camera looking / unclearing recording field 2204 record whether the person to be photographed is smiling, showing their teeth, and looking at the camera at the time of photography, respectively. The face direction recording field 2205 records the face direction of the person to be photographed.

[0164] The correction necessary / unnecessary recording field 2206 records whether or not the photographed data needs to be corrected. Information indicating the degree of correction possible may also be recorded additionally. The data format recording field 2207, size format recording field 2208, and resolution recording field 2209 are referenced by the store terminal 5, and delivery data is created according to this information. A specific sample may be recorded in the sample recording field 2210, and detailed photographing conditions may be recorded in the specification detail recording field 2211. The sample recording field 2210 and the specification detail recording field 2211 may record links to storage locations in the management device 2 for detailed specifications and photographing conditions.

[0165] Using the information recorded in these databases, processing equivalent to the reservation processing of Fig. 2 and the processing during shooting of Fig. 4 in the first embodiment is performed. Note that in this embodiment, some of these processes in the first embodiment may be omitted or replaced with other processes. For example, in the reservation processing of Fig. 2, the processing related to the selection of a shooting plan in steps S206 and S207 may be omitted. In the processing during shooting of Fig. 4, the processing for inputting additional information in step S402 may be omitted.

[0166] 8 is performed if it is recorded as necessary in the data provision necessity record field 2101 for the photographed person. Otherwise, it is performed to the client terminal 6 after each member has finished photographing. The photographed data may be sent to the client terminal 6 by any method, such as via a download site or as an email attachment.

[0167] In this way, in principle, photo reservations and photo shooting are performed by the same processes as in the first embodiment, but delivery of the photographed data and billing are all made to the client terminal 6 at once.

[0168] 23 is a flowchart of member management control. In the flowchart shown in this figure, the reservation status of each member is checked from the client terminal 6. Depending on the reservation status, reminders and the like are sent to user terminal 4E operated by an unreserved person who has no photo shoot reservation due to a cancellation after reservation, user terminal 4F operated by an unregistered person who has not made an initial reservation, and user terminal 4G of a member who canceled without permission.

[0169] In step S2301, the client terminal 6 accesses the management device 2 and requests that a list of group members be displayed, and in step S2302 the management device 2 converts the group member management database 2400 into a displayable format. Then, in step S2303, the client terminal 6 accesses the management device 2, thereby becoming able to refer to the group member list database 2400.

[0170] 24 is a diagram showing an example of a group member management database 2400. The group member management database 2400 is created for each group ID recording column 1801. Therefore, the group ID recording column 1801 and group name recording column 1802 are shown at the top of the group member management database 2400.

[0171] Also, at the bottom, there are recorded a member ID record column 2401, a name record column 2402, an employee number record column 2403, a reservation store record column 2404, a reservation date and time record column 2405, a photo shoot date and time record column 2406, a same-day cancellation record column 2407, and an unauthorized cancellation record column 2408.

[0172] The member ID record column 2401, name record column 2402, and employee number record column 2403 record information about the member who accepted the photography reservation, and the reservation store record column 2404, reservation date and time record column 2405, and photography date and time record column 2406 record specific reservation details.

[0173] The same-day cancellation record field 2407 records the date and time when the cancellation process was carried out on the day of the reservation, and the no-show cancellation record field 2408 records the date and time when the cancellation was confirmed because the customer did not show up despite having made a reservation.

[0174] 23 again, in step S2311, the client terminal 6 refers to the group member management database 2400 to check whether there are any members for whom there is no reservation information. If there are any members for whom there is no reservation information, such as member ID: 002 in the example of FIG. 24, the client terminal 6 requests the management device 2 to send a photo shoot reservation reminder to such members. Thereafter, in step S2312, the management device 2 sends a reminder to the user terminal 4E operated by the member for whom there is no reservation information.

[0175] In step S2321, the client terminal 6 compares the list with a list of group members managed separately to check for members who are not recorded (registered) in the group member management database 2400. If there are any unregistered members, in step S2322 the client terminal 6 directly transmits a reminder to the user terminal 4F operated by such members.

[0176] In step S2331, the client terminal 6 checks whether there are any members who have canceled without notice by referring to the no-show cancellation record column 2408 of the group member management database 2400. If there is a member who has canceled without notice, such as member ID: 003 in the example of Fig. 24, in step S2332 the client terminal 6 may directly send a confirmation email to that member.

[0177] In this way, the client terminal 6 can easily manage members by using the group member management database 2400. In the process of step S1706, etc., the client terminal 6 can register in advance a list of members associated with a predetermined group ID, for example, using a member list in CSV format. By using this method, it is possible to prevent unregistered members from occurring. Even if the member list is registered in advance, reservations may be processed based on the information in the reservation URL record field 1808. In such cases, for example, if it is determined that the member is included in the pre-registered members using an ID number or the like, it may be processed as reservation information for the predetermined member, and if it is determined that the member is not included, the reservation information may be additionally recorded as made by a member associated with the predetermined group ID.

[0178] (Variation) The following describes a modified example in which the second embodiment described with reference to FIGS. 16 to 24 is realized in another manner.

[0179] FIG. 25 is a flowchart showing the processing performed in the management system 1 in the modified example.

[0180] In step S2501, the head office terminal 3 or the client terminal 6 inputs the photographing conditions, reservation display control information, and reservation restriction information to the management device 2.

[0181] The photographing conditions are information recorded in the store confirmation information database 2100 and the photographing information database 2200, and are used when photographing in the store and generating delivery images (S2505).

[0182] The reservation display control information is information recorded in the note record column 1901 of the group special notes database 1900, the ID number display necessity record column 2005 in the reservation form information database 2000, the ID number replacement character record column 2006, etc., and is used when generating the reservation page (S2502).

[0183] The reservation restriction information is information recorded in the reservation-available store record column 1903 in the group special notes database 1900, the reservation-available period record column 2003, the photography-available period record column 2004, the employee number regular expression record column 2007, etc. in the reservation form information database 2000, and is used to restrict input when accepting a photography reservation (S2505).

[0184] Note that the input of some or all of the photography conditions, reservation display control information, and reservation restriction information in step S2501 may be performed by at least one of the head office terminal 3, the client terminal 6, and the user terminal 4. For example, some of the photography conditions may be input by the user terminal 4 operated by a group member rather than by the client terminal 6 operated by the client administrator, thereby reducing the burden on the client administrator. Also, some of the reservation restriction information may be configured to be accessible from the user terminal 4 of a leader among the members (e.g., a person in a managerial position), or may be linked to the scheduler of the user terminal 4. In this way, the photography conditions, reservation display control information, and reservation restriction information can be received from any terminal.

[0185] Furthermore, in step S2501, the management device 2 may receive in advance a list of members associated with a predetermined group ID. Even if the list of members is registered in advance, when a reservation is received from a member other than the registered members (steps S2504 and S2505), as described below, the reservation may be added to the group members as a reservation made by a member belonging to the group.

[0186] In step S2502, the management device 2 uses the reservation display control information to create a reservation page that accepts reservations from members. The reservation page is displayed based on the reservation display control information. For example, the display is based on the contents recorded in the note record field 1901. Furthermore, to prevent members from making input errors when entering their own IDs (talent numbers or employee numbers), the display is based on the contents recorded in the ID number display necessity record field 2005, the ID number replacement character record field 2006, etc.

[0187] In step S2503, the management device 2 provides the URL of the generated reservation page to the user terminal 4 via the client terminal 6 (or the head office terminal 3). In step S2504, the user terminal 4 accesses the management device 2, selects one of the multiple stores, and makes a photo shoot reservation using information unique to the member who is the operator of the user terminal 4. In step S2505, the management device 2 records the content of the accepted photo shoot reservation in association with the member who is the operator of the user terminal 4.

[0188] Here, the management device 2 limits the stores that can be reserved for photography based on the reservation available store record field 1903, and accepts reservation input only for the period corresponding to the reservation available period record field 2003, and accepts photography at stores for the period corresponding to the photography available period record field 2004. Furthermore, the management device 2 only accepts input of member IDs that comply with the regular expression record field 2007.

[0189] In step S2506, before starting shooting at the store, the store terminal 5 accesses the management device 2 and refers to the shooting conditions. The shooting conditions include, for example, the cut information record field 2107 of the store confirmation information database 2100, the background color record field 2201 of the shooting information database 2200, the smiling / unsmiling record field 2202, the teeth showing record field 2203, the looking at the camera record field 2204, the face direction record field 2205, the correction required record field 2206, the data format record field 2207, the size format record field 2208, and the resolution record field 2209. The sample record field 2210 and the detailed specification record field 2211 may also be referred to.

[0190] In step S2507, when the photographing according to the photographing conditions is completed, the store terminal 5 creates photographic data that meets the delivery standards such as the format according to the photographing conditions. Then, in step S2508, the store terminal 5 uploads the photographic data to the management device 2.

[0191] Then, in step S2509, the management device 2 determines whether the photographic data accepted in step S1503 meets the delivery criteria. This process is equivalent to step S1506 in Fig. 15, but the management device 2 may determine any delivery criteria based mainly on the photography information database 2200, as well as on various databases such as the photography conditions and format of the photographic data (the cut information record field 2107 of the store confirmation information database 2100).

[0192] In step S2510, when photographing of each member is completed, the management device 2 prepares to provide the image data by associating the image data recorded corresponding to the members with each group and recording them together. Note that recording the image data of members in association with their groups does not necessarily mean that the image data is registered in a single folder, but rather the image data may be associated with a group ID, allowing the management device 2 to collectively reference the image data of all members associated with that group ID. Alternatively, associating the members with the group ID may result in the image data and the group ID being associated, and it is sufficient that the configuration is such that the image data of all members can be obtained using the group ID.

[0193] The management device 2 then provides the photo data of each member to the client terminal 6. The provided photo data may be, for example, named according to a naming rule in the file name rule record field 2106 of the store confirmation information database 2100, or may have a file name including the employee number accepted at the time of reservation. A bill summarizing the photography fees for each member may also be sent together with the photo data. The photo data of such group members does not have to be sent by the management device 2; instead, the management device 2 may refer to and obtain image data of the members using the group ID, and send it as an attachment to an email or the like.

[0194] Furthermore, as shown in step S2511, the management device 2 may record the cancellation history in advance in the group member management database 2400 when a member's reservation is canceled, and create a member management list based on the group member management database 2400. In step S2502, the management device 2 provides the member management list to the client terminal 6. The operator of the client terminal 6 can access unregistered members and canceled members based on the member management list.

[0195] It should be noted that a plurality of functionally different functional blocks that perform the above-described processes may be provided in the control unit of the management device 2. That is, the management device 2 may be provided with functional blocks such as a photography condition receiving unit that receives and records photography conditions for photography, a photography reservation receiving unit that receives and records photography reservations from the user terminal 4, an image data receiving unit that receives and records image data transmitted from the store terminal 5, and a group association unit that further associates image data recorded in association with members with groups.

[0196] According to the second embodiment, the following effects can be obtained.

[0197] In the second embodiment of the method for managing multiple photo studios, shooting conditions are accepted and recorded (S2502), a photo shoot reservation at one of multiple photo studios selected from a user terminal 4 (member terminal) is accepted and recorded (S2504), image data generated by shooting under the referenced shooting conditions is accepted from a store terminal 5 installed in the selected photo studio and recorded in association with the member's photo shoot reservation (S2505), and the image data recorded corresponding to each member is recorded together as a group (S2506).

[0198] With this management method, the shooting conditions for multiple photo shoots can be accepted with a single operation, and the accepted shooting conditions can be commonly referenced at any photo studio reserved from the member terminal, allowing the reservationr to obtain photo data in which the person being photographed. In this way, even when multiple photo studios are used, image data of the same quality can be delivered.

[0199] Furthermore, the client terminal 6 operated by the group manager does not need to input reservations for each member, and each member can make reservations at their favorite store according to their own convenience. Furthermore, by recording image data of all members in association with the group, it becomes easy to deliver this photo data collectively to the client terminal 6, eliminating the need for the group manager to collect image data within the group.

[0200] In the method for managing multiple photo studios according to the second embodiment, the input of photography conditions (S2501) is performed from at least one of the user terminal 4 (member terminal), the client terminal 6 (group management terminal), and the head office terminal 3 (studio management terminal) operated by the photo studio manager. By allowing input of some or all of the photography conditions from any terminal in this way, the input work can be distributed according to the workload of the person in charge of each terminal.

[0201] For example, if the group manager has limited human resources, the number of items accepted from the photo studio's head office terminal 3 will be increased. If the group manager has limited human resources but cannot increase the number of items accepted from the photo studio's head office terminal 3 due to budgetary or other reasons, the number of items accepted from the user terminal 4 will be increased. In this way, by configuring each item to be input from any terminal, the input work of items can be optimized according to the workload of the operator of each terminal.

[0202] In the second embodiment of the method for managing multiple photo studios, a reservation acceptance means (reservation page) is further provided for use when accepting photo shoot reservations from members (S2502, S2503), and photo shoot reservations are made using the reservation acceptance means (reservation page) from a user terminal 4 (member terminal) (S2504, S2505).

[0203] By providing a reservation acceptance means in this way, it becomes easy to input the association of the relationship with the group when accepting a reservation from the user terminal 4, and it becomes easy to associate the user who made the reservation with the photography conditions. Note that although an example of the reservation acceptance means is a reservation page, it is not limited to this and any means for associating a photography reservation with a group may be used, such as input of common login information or a common code.

[0204] The method for managing multiple photo studios according to the second embodiment further receives reservation display control information for controlling the display content of the reservation page (S2501), and generates a reservation page based on this reservation display control information (S2505).

[0205] When accepting reservations from group members on the reservation page, the information entered varies for each group. For example, the input items differ depending on the group, such as talent number, employee number, phone number, etc. Therefore, by accepting reservation display control information and generating the reservation page screen using the reservation display control information, it is possible to prompt members to enter the input items that the client deems necessary.

[0206] The method for managing multiple photo studios according to the second embodiment further receives reservation restriction information used to restrict the acceptance of photography reservations (S2501), and when accepting photography reservations from the user terminal 4, restrictions are imposed based on the reservation restriction information. In this way, input from members will not be accepted that is not related to the items desired by the client, so it is possible to encourage the input of appropriate reservation information.

[0207] In the second embodiment of the method for managing multiple photo studios, this information limits the photo studios that can be used for group photo shoot reservations. While each studio offers different levels of photo quality, for example, if the same staff work at multiple studios located close to each other, the quality of the photos produced at those studios is often similar. By pre-determining which studios can be booked based on the photography skills and equipment of each studio, the quality of the final photo data can be made more similar.

[0208] In the second embodiment of the method for managing multiple photo studios, when a photo shoot reservation is canceled, a cancellation history is recorded, and the cancellation history recorded corresponding to each member is recorded collectively for the group. This makes it possible to provide the cancellation history corresponding to each member to the group management terminal. This allows reminders to be sent from the group management terminal to each member's user terminal 4, thereby more appropriately managing the reservation status of each member.

[0209] The present invention allows various embodiments and modifications without departing from the broad spirit and scope of the present invention. Furthermore, the above-described embodiments are intended to illustrate the present invention and do not limit the scope of the present invention. That is, the scope of the present invention is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and within the scope of the meaning of the invention equivalent thereto are considered to be within the scope of the present invention. [Explanation of symbols]

[0210] 1 Management System 2 Management device 3 Headquarters terminal (studio management terminal) 4 User terminal (member terminal) 5. Store terminals 6 Client terminals (group management terminals)

Claims

1. A method for managing a plurality of photo studios, performed by a photo studio management device, comprising: Accept and record reservation information including the content of the photo shoot at one of the selected photo studios and the user's contact information from a user terminal operated by the user; receiving image data obtained by photography according to the photography content from a store terminal installed in the photo studio that references the photography content; determining, when receiving the image data, whether or not the image data meets a delivery standard according to the photography content; and, if the image data meets the delivery standard, recording the image data in association with the reservation information; A photo studio management method in which the recorded image data is provided using the contact information of the user included in the reservation information.

2. The photo studio management method according to claim 1 , wherein the delivery standard relates to a format of the image data.

3. The photo studio management method according to claim 2 , wherein the delivery criteria further include criteria regarding the identity of the subject shown in the image data and the user.

4. providing the image data to the user terminal after receiving an operation of consenting to the conditions for providing the image data from the user terminal; The photo studio management method according to claim 1 , further comprising providing a history of said consent operations to said user terminal.

5. When providing the image data, the user provides introduction information to be used in introducing the photography to other users who will be introduced. receiving and recording the reservation information associated with the introduction information from an introduced person terminal operated by the introduced person who has received the introduction information from the user; The photo studio management method according to claim 1, wherein after providing the photo data of the introduced person to the introduced person, the introduction benefit is provided by contacting the contact information included in the reservation information of the user who made the introduction.

6. A management device for a plurality of photo studios, comprising: a reservation information receiving unit that receives and records reservation information including the content of photography at one of the selected photo studios and the user's contact information from a user terminal operated by the user; an image data receiving unit that receives image data obtained by photography according to the photography content from a store terminal installed in the photo studio that references the photography content, determines whether the image data meets delivery standards according to the photography content when receiving the image data, and if the image data meets the delivery standards, records the image data in association with the reservation information; a photo studio management device comprising: an image data providing unit that provides the recorded image data using the contact information of the user included in the reservation information;

7. A management system including a management device for managing a plurality of photo studios, a user terminal operated by a user, and a store terminal installed in the photo studio, The management device Accept and record reservation information from the user terminal, the reservation information including the content of the photo shoot at one of the selected photo studios and the user's contact information; Accepting image data obtained by photography according to the photography content from the store terminal that references the photography content, determining whether or not the image data meets a delivery standard according to the photography content when accepting the image data, and if the image data meets the delivery standard, recording the image data in association with the reservation information; A photo studio management system that provides the recorded image data using the user's contact information included in the reservation information.

Images