JP2021170336A - System for smartly storing and managing electronic data - Google Patents

Abstract

To provide a system for smartly managing daily generated electronic data.SOLUTION: An electronic data management system 1 allows an upload module 32 held in a user terminal 30 to upload electronic data stored in the user terminal in an electronic data management server 10, and allows an archive module 13 held in the electronic data management server 10 to automatically execute archive processing. The electronic data management system includes a notification module 22 held in a life and death information management server 20 for managing life and death information indicating life and death of a user. The notification module notifies a notification indicating that a user dies to a user terminal, automatically erases user electronic data stored in the user terminal, notifies the notification indicating that the user dies to the electronic data management server, and automatically erases the user electronic data stored in the electronic data management server.SELECTED DRAWING: Figure 1

Description

The present invention relates to a system for storing and managing electronic data such as images, moving images, characters, and music.

Currently, various electronic data such as images, videos, characters, and music are generated in large quantities by individuals and corporations. For example, people now carry smartphones equipped with high-performance cameras on a daily basis and take pictures of people and landscapes here and there to generate large amounts of image data. In companies, it is common for materials to be created on a personal computer, and a large amount of text data is generated.

Such electronic data is usually stored in the internal memory of each person's computer or smartphone, or is an external physical recording medium such as a hard disk drive (HDD) or SD card connected to the computer via an interface such as USB. It may be saved (recorded) in. However, HDDs and SD cards are not guaranteed to be usable forever, and may become unreadable due to physical or logical failures.Therefore, users should back up or use recording media to protect their data. It is necessary to be aware of replacement by purchase.

Against this background, services that store electronic data on cloud servers by uploading electronic data owned by individuals and corporations to cloud servers via the Internet have become widespread. By issuing an ID and password for each user on the cloud server, each of a plurality of users can safely manage their own data on the cloud server. Since the cloud server provider maintains the recording medium on the cloud, users need to worry that their electronic data will become unreadable or disappear due to physical or logical failures. No. An example of such a cloud service is disclosed in Patent Document 1.
Japanese Unexamined Patent Publication No. 2016-212293

As described above, the storage management method of electronic data generated by the user is diversified and sophisticated, but further improvement is desired. For example, if electronic data is continuously stored on the storage for a long period of time, the electronic data will only accumulate on the storage. The accumulated electronic data has a risk of loss due to a storage failure, etc., and it is necessary for the user to make an effort to back it up.

In addition, the electronic data stored by the user on a personal computer, smartphone, or cloud server becomes what is called a "digital relic" or "digital heritage" when the user dies. Electronic data is related to user privacy, and there may be electronic data that the bereaved family does not want to see after death. Therefore, post-mortem processing of electronic data held by the user is an issue.

In view of the above circumstances, an object of the present invention is to provide a system capable of smarter storage and management of electronic data generated on a daily basis.

According to one aspect of the present invention, the system for managing electronic data includes a cloud server to which a storage area for storing electronic data is allocated for each usage ID, and electronic data is stored for each usage ID. The cloud server holds the archive condition, which is the condition for archiving, and the cloud server accepts the upload of electronic data from the user terminal signed in with a certain usage ID via the Internet, and the uploaded electronic data is uploaded at the upload source. It is saved in the storage area assigned to the usage ID of a certain user terminal, and it is determined for each usage ID whether or not the archiving conditions are satisfied. If a positive determination is made, the determination is made in response to this. The archive process for archiving the electronic data stored in the storage area assigned to the assigned usage ID is automatically executed. Further, according to one aspect of the present invention, the system for managing electronic data includes an upload module held in a user terminal having a storage area for storing electronic data, and is a condition for archiving electronic data. The archive condition is retained, the upload module signs in to the cloud server with a certain usage ID via the Internet, the upload module determines whether or not the archive condition is satisfied, and a positive determination is made. In response to this, the system automatically uploads the electronic data stored in the storage area to the cloud server, and the cloud server performs an archiving process for archiving the uploaded electronic data. Run automatically. In the archive process, the portable storage medium in which the electronic data is written is delivered to the user corresponding to the usage ID, and the printed matter generated by printing the electronic data is delivered to the user corresponding to the usage ID. This includes one of the above and the delivery of a photobook generated by arranging electronic data according to a predetermined layout to a user corresponding to the usage ID.

According to one aspect of the present invention, the system for managing electronic data includes a notification module held in a cloud server and an erasing module held in a user terminal having a storage area for storing electronic data, and has a usage ID. In an environment in which the user information including the life / death information of the user indicated by the usage ID is retained in the cloud server and the user terminal signs in to the cloud server by the usage ID via the Internet. When the life / death information is updated to the information indicating death on the user information, the notification module automatically sends a notification indicating the update to the user terminal in response to the update, and the erasing module causes the erasing module. , The electronic data stored in the storage area is automatically deleted in response to the notification. Further, according to one aspect of the present invention, the system for managing electronic data is a second cloud server having a notification module held in the first cloud server and a storage area for storing electronic data for each usage ID. The notification module is provided with a retained erasing module, and the user information including the life / death information of the user indicated by the usage ID is stored in the first cloud server in association with the usage ID, and the notification module is provided via the Internet. When the life-and-death information is updated to information indicating death on the user information, in response to this, a notification indicating the update is automatically transmitted to the second cloud server, and the erasing module performs the notification. In response to this, the electronic data stored in the storage area associated with the usage ID whose death is indicated by the notification is automatically deleted.

According to the present invention, electronic data generated on a daily basis can be managed smarter.

FIG. 1 is a diagram showing an electronic data management system according to an embodiment. FIG. 2 is a diagram showing a state in which electronic data is grouped and stored in an electronic data management server in the electronic data management system according to the embodiment. FIG. 3 is a diagram showing a state in which electronic data is grouped and stored in a user terminal in the electronic data management system according to the embodiment. FIG. 4 is a diagram showing an example of user information associated with a usage ID in the electronic data management system according to the embodiment. FIG. 5 is a diagram schematically showing a configuration example of an archive module in the electronic data management system according to the embodiment. FIG. 6 is a flowchart showing a procedure for confirming the archive processing with the user in the electronic data management system according to the embodiment. FIG. 7 is a diagram schematically showing a configuration example of an upload module in the electronic data management system according to the embodiment. FIG. 8-1 shows a detailed process in the case of storing electronic data in a physical storage medium in the archive process of the electronic data management system according to the embodiment. FIG. 8-2 shows detailed processing in the case of creating a photobook from electronic data which is image data (photograph data) in the archiving processing of the electronic data management system according to the embodiment. FIG. 8-3 shows a detailed process of printing on the shipping label in the archive process of the electronic data management system according to the embodiment. FIG. 9 shows an example of user information associated with a usage ID managed by a life-and-death information management server in the electronic data management system according to the embodiment. FIG. 10-1 is a flowchart showing an example of processing of the notification module and the erasing module in the electronic data management system according to the embodiment. FIG. 10-2 is a flowchart showing an example of processing of the notification module and the erasing module in the electronic data management system according to the embodiment. FIG. 11 is an example showing a GUI for user confirmation displayed on a user terminal in the electronic data management system according to the embodiment. FIG. 12 is an example showing a GUI for user confirmation displayed on a user terminal in the electronic data management system according to the embodiment. FIG. 13 is an example showing a GUI for user confirmation displayed on a user terminal in the electronic data management system according to the embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a system 1 according to an embodiment of the present invention. The system 1 includes an electronic data management server 10, a life-and-death information server 20, and a user terminal 30. The user terminal 30 is a terminal device used by a user such as a personal computer (personal computer), a smartphone, or a digital camera, and can process electronic data held in a built-in storage medium or a connected external storage medium. It is a terminal device that can be used. The electronic data management server 10 is a server on the Internet, and is configured to accept uploads of electronic data from a user terminal 30 and execute an archive process for archiving the uploaded electronic data. The life-and-death information management server 20 is a server on the Internet that manages information on the life and death of the user of the user terminal 30.

The electronic data management server 10 and the user terminal 30 are connected via the communication channel C1. Communication channel C1 includes, for example, Internet connection communication via the Internet. The life-and-death information management server 20 and the user terminal 30 are connected via the communication channel C2. Communication channel C2 includes, for example, Internet connection communication via the Internet. The life-and-death information management server 20 and the electronic data management server 10 are connected via the communication channel C3. Communication channel C3 includes, for example, Internet connection communication via the Internet.

The user terminal 30 is a computer terminal such as a personal computer (personal computer), a smartphone, or a digital camera. The user terminal 30 includes a storage medium 31 (local storage 31) such as a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), and an SD card. The user terminal 30 includes a processor that processes electronic data held in the storage medium 31. Processing of electronic data includes, for example, reproduction of electronic data. The user terminal 30 has a function of storing electronic data in the storage medium 31. For example, the user terminal 30 is provided with a camera, and when a camera is used for shooting, the image data generated by the shooting is stored in the storage medium 31 in response to the shooting. For example, the user terminal 30 stores image data, music data, and the like downloaded from an external server via the Internet in the storage medium 31. The user terminal 30 has a function of uploading electronic data in the storage medium 31 to the electronic data management server 10 via the communication channel C1 on a regular or irregular basis. For example, the user terminal 30 uploads electronic data in response to an instruction from the user. The user terminal 30 uploads electronic data, for example, when the remaining capacity of the storage medium 31 becomes a certain amount or less. The user terminal 30 accepts, for example, a setting of an upload schedule (for example, once a month) and uploads electronic data based on the schedule. The user terminal 30 uploads electronic data according to, for example, archiving conditions described later.

The system 1 includes user information 50 that manages the user's name, address, archive conditions, and the like of the user terminal 30. The user information 50 includes the name, address, archive conditions, and the like of the user in association with the usage ID that uniquely identifies the user of the user terminal 30. The usage ID is, for example, an ID issued by the electronic data management server 10 or the life / death information management server 20, and is an ID for receiving a service from the electronic data management server 10 or the life / death information management server 20. For example, the electronic data management server 10 accepts a sign-up from the user terminal 30, issues an arbitrary ID or an ID input from the user terminal 30 as a usage ID for accessing the electronic data management server 10, and registers it. .. For example, the life-and-death information management server 20 receives a sign-up from the user terminal 30, issues an arbitrary ID or an ID input from the user terminal 30 as a usage ID for accessing the life-and-death information management server 20, and registers it. .. The user terminal 30 stores the usage ID registered by the user (the usage ID issued by the electronic data management server 10 and the life / death information management server 20), and stores the electronic data in the storage medium 31 in association with the usage ID. Upload. The user terminal 30 is used in a state of being signed in to the electronic data management server 10 and the life / death information management server 20 using the usage ID registered by the user. In the example shown in FIG. 1, the user terminal 30 is associated with the usage ID "USR001", and the user terminal 30 signs in to the electronic data management server 10 and the life / death information management server 20 with the usage ID "USR001". doing. The user information 50 may be held somewhere on the system 1, and as an example, it may be held by the electronic data management server 10 or may be held by the user terminal 30. The electronic data management server 10 can refer to at least a part of the user information 50, and the user terminal 30 can also refer to at least a part of the user information 50.

The electronic data management server 10 allocates a storage area for electronic data on the database 11 for each usage ID. The electronic data management server 10 accepts sign-in by the user ID from the user terminal 30 and accepts upload of electronic data. The electronic data management server 10 stores the uploaded electronic data in a storage area on the database 11 corresponding to the upload source usage ID (signed-in usage ID). In the example shown in FIG. 1, a storage area corresponding to the usage ID "USR001" and the usage ID "USR002" is assigned to the database 11, and four electronic data files are assigned to the storage area of the usage ID "USR001". Is stored, and three electronic data files are stored in the storage area of the usage ID "USR002". The electronic data management server 10 continuously accepts uploads of electronic data files from the user terminal 30 related to the same usage ID for a long period of time, and the storage area allocated to the usage ID. Multiple electronic data files can be stored in the server.

The electronic data management server 10 can group a plurality of electronic data to be stored in the storage area allocated for each usage ID. Grouping includes, for example, attaching a tag (label) to each group, creating a folder for each group, and assigning a name (tag name, folder name, etc.) indicating the group. The electronic data management server 10 accepts input of an arbitrary name from the user terminal 30, registers the accepted name as a group name, and stores the electronic data in groups. FIG. 2 shows an example in which eight electronic data files belonging to a group named “family photograph” are stored in the storage area corresponding to the usage ID “USR001”. When grouped into a plurality of groups, when the electronic data management server 10 accepts the upload of electronic data from the user terminal 30, the electronic data management server 10 accepts the designation of the group as the save destination, and the uploaded electronic data belongs to the designated group. Save the data.

Similarly, the user terminal 30 can group a plurality of electronic data to be stored on the storage medium 31. Grouping includes, for example, attaching a tag (label) to each group, creating a folder for each group, and assigning a name (tag name, folder name, etc.) indicating the group. The user terminal 30 accepts an input of an arbitrary name from the user via the input unit, registers the accepted name as a group name, and stores the electronic data in groups. FIG. 3 shows an example in which six electronic data files belonging to a group named “travel photograph” are stored in the storage medium 31 of the user terminal 30 holding the usage ID “USR001”. When grouped into a plurality of groups, the user terminal 30 accepts the designation of the group as the save destination when saving the electronic data in the storage medium 31, and saves the electronic data so as to belong to the designated group.

The user information 50 includes name information in association with the usage ID. The name information is input by the user through the user terminal 30. The user information 50 includes address information in association with the usage ID. The address information is the address information indicating the address as the destination of the package to the user, and is input by the user through the user terminal 30. Further, the user information 50 includes an archive condition in association with the usage ID. The archive condition is information indicating the condition for archiving electronic data. The archiving condition is, for example, a time condition for archiving, for example, a condition such as "the first day of every month". In this case, the archiving condition indicates that the electronic data is archived once a month on a predetermined day (the first day of each month). Preferably, the timely archiving condition comprises at least one of year, month and day. Further, the archive condition is, for example, a capacity condition for archiving, for example, a condition such as "10 GB". In this case, the archiving condition indicates that every time the amount of stored electronic data reaches 10 GB (gigabytes), it is archived. The archiving condition is, for example, a quantitative condition for archiving, for example, a condition such as "100 pieces". In this case, the archiving condition indicates that the archive is performed every time the number of stored electronic data files reaches 100.

As an example, the user information 50 is generated by the user terminal 30. The user terminal 30 accepts the input of the name information, the address information, and the archive condition, and generates the user information 50 by associating the input name information, the address information, and the archive condition with the usage ID. The user terminal 30 transmits the user information 50 to the electronic data management server 10 through the communication channel C1 and causes the electronic data management server 10 to hold the user information 50. As another example, the user information 50 is generated by the electronic data management server 10. The user terminal 30 accepts input of name information, address information, and archive conditions while signed in to the electronic data management server 10, and transfers the input name information, address information, and archive conditions to the electronic data management server 10. Send. The electronic data management server 10 generates and holds the user information 50 by associating the received name information, address information, and archive conditions with the usage ID, and transmits the user information 50 to the user terminal 30 through the communication channel C1. Alternatively, the user information 50 is generated by a method combining these. FIG. 4 is a diagram showing an example of user information 50. FIG. 4 shows an example of user information associated with the usage ID “USR001”. In the example shown in FIG. 4, in the user information 50, the information (50a) indicating the usage ID "USR001", the name information (50b) indicating the user's name of the usage ID "USR001", and the address of the usage ID "USR001". The information (50c) and the archive condition (50d) of the usage ID "USR001" are associated with each other.

The electronic data management server 10 includes an archive module 13. The archive module 13 is a functional element including a computer program. The archive module 13 is configured to execute an archive process for archiving the electronic data stored in the storage medium 31 of the user terminal 30 and the electronic data stored in the database 11 in a physical medium for each usage ID. Has been done.

The user terminal 30 includes an upload module 32. The upload module 32 is a functional element that includes a computer program. The upload module 32 is configured to upload the electronic data in the storage medium 31 to the electronic data management server 10 via the communication channel C1.

(Archive processing: first aspect)
Here, the archive process according to the first aspect executed by the archive module 13 will be described in detail. In the archive process according to the first aspect, the electronic data management server 10 confirms the archive conditions and determines whether or not the archive process is necessary. According to the first aspect, the upload module 32 uploads the electronic data stored in the storage medium 31 to the electronic data management server 10 regardless of the archiving conditions. For example, the upload module 32 automatically responds to each time electronic data is generated by the user terminal 32 and stored in the storage medium 31 (for example, every time image data is generated by taking a picture with a camera). The electronic data is uploaded to the electronic data management server 10. Alternatively, the upload module 32 automatically uploads the electronic data in the storage medium 31 periodically, for example, once a month. Further, for example, the upload module 32 may upload based on the user's intention, and in this case, the selected electronic data is electronically selected according to the selection operation in which the user selects the electronic data stored in the storage medium 31. Upload to the data management server 10. The upload module 32 uploads electronic data together with the usage ID held in the user terminal 30. Each time the electronic data management server 10 receives the uploaded electronic data, the electronic data management server 10 stores the electronic data in the storage area on the database 11 assigned to the received usage ID. The archive module 13 performs an archive process on the electronic data stored in the database 11. FIG. 5 is a diagram schematically showing the configuration of the archive module 13 according to the first aspect. As shown in FIG. 5, the archive module 13 has a determination process S131 and an archive process S132. In the determination process S131, the archive condition (50d) is referred to for each usage ID (50a) of the user information 50, and it is determined whether or not to archive the stored electronic data corresponding to the usage ID. The archive module 13 may refer to the archive condition (50d) of the usage ID and execute the determination process S131 in response to saving the new electronic data uploaded by the user of the usage ID. The archive module 13 may periodically (for example, at a fixed time every day) execute the determination process S131 with reference to the archive conditions (50d) of all the usage IDs (50a) in the user information 50.

When the determination process S131 determines that an archive is required for a certain use ID, the archive module 13 executes an archive process for the use ID (S132). As an example, the archiving process includes storing electronic data in a physically portable storage medium such as a CD-R, DVD-R, USB memory, or SD card, and shipping the storage medium to a user. As an example, the archiving process includes sending a printed matter (photograph) on which the image data is printed to the user when the electronic data is image data (photograph data). As an example, in the archive process, when the electronic data is image data (photo data), a plurality of image data are arranged in a predetermined layout and printed to create a photo book, and the photo book is sent to the user. include. The shipping includes referring to the name information (50b) and the address information (50c) associated with the usage ID (50a), and shipping to the destination including the name and address. In the archive process S132, the archive module 13 adds meta information (flags, tags, etc.) indicating that the electronic data that has undergone the archive process is “archived”. Meta information is added, for example, in file units of electronic data. As a result, each time the archive module 13 executes the archive process S132, the archive module 13 selects only the electronic data to which the "archived" meta information is not added (electronic data that has not been archived in the past) and performs the archive process. Can be executed. Further, also in the determination process S131, the determination process can be performed only on the electronic data to which the "archived" meta information is not added (electronic data that has not been archived in the past and has not been archived).

A specific example of the determination process S131 and the archive process S132 when the archive condition is a temporal rule is shown. In the determination process S131, the archive module 13 acquires the current date and time from, for example, the hardware clock or the system clock, refers to the archive condition (50d) corresponding to each usage ID (50a), and archives each usage ID (50a). Determine if it is time to do. For example, if the archiving condition of a certain usage ID indicates "Archive once a month on the first day", when the current date is the first day of a certain month, the user of the usage ID saves it. It is determined that it is necessary to archive the electronic data. For example, if the archiving condition for a certain usage ID is "Archive one month after the last archive", the current date obtained is one month after the last archive. Then, it is determined that it is necessary to archive the electronic data stored by the user of the usage ID. In the archive process S132, the archive process is executed by selecting only the electronic data in the storage area corresponding to the usage ID determined to be required to be archived in S131 to which the "archived" meta information is not added. do. As a result, the archive process S132 is executed every time the time indicated by the archive condition comes and the determination process S131 determines that archiving is necessary. At this time, the electronic data that has not been archived (that is, the previous one) The electronic data that has increased after being determined by the determination process S131 and archived) can be newly archived.

A specific example of the determination process S131 and the archive process S132 when the archive condition is a capacity rule is shown. In the determination process S131, the archive module 13 derives the capacity of the stored electronic data of the electronic data to which the "archived" meta information is not added, and sets the capacity (threshold value) as a condition for archiving. By comparison, it is determined that archiving is necessary if there is a match or excess. That is, the amount of electronic data that has increased since the last archive is derived and determined. For example, when the archive condition indicates "10 GB" and the capacity of the derived unprocessed archived electronic data is 10 GB or more, it is determined that archiving is necessary. The archive module 13 executes the determination process S131 on the electronic data of all usage IDs at predetermined date and time (for example, 1:00 am every day) by referring to the hardware clock or the system clock, for example. Alternatively, the determination process S131 may be executed on the electronic data of the upload source's usage ID each time a new upload of electronic data is received from the user terminal 30. In the archive process S132, the archive process is executed for the electronic data whose capacity is derived in the determination process S131 (that is, the electronic data to which the "archived" meta information is not added in the storage area).

A specific example of the determination process S131 and the archive process S132 when the archive condition is a quantitative rule is shown. In the determination process S131, the archive module 13 is a condition for deriving and archiving the quantity (for example, the number of files) of the stored electronic data to which the "archived" meta information is not added. It is determined that archiving is necessary if it matches or exceeds the quantity (threshold) that exists. That is, the number of electronic data files that has increased since the previous archive is derived and determined. For example, when the archive condition indicates "100 pieces", and the quantity of the derived unprocessed archived electronic data is 100 pieces or more, it is determined that archiving is necessary. The archive module 13 executes the determination process S131 on the electronic data of all usage IDs at predetermined date and time (for example, 1:00 am every day) by referring to the hardware clock or the system clock, for example. Alternatively, the determination process S131 may be executed on the electronic data of the upload source's usage ID each time a new upload of electronic data is received from the user terminal 30. In the archive process S132, the archive process is executed for the electronic data whose quantity is derived in the determination process S131 (that is, the electronic data to which the "archived" meta information is not added in the storage area).

In the archive processing S132, all the electronic data that has not been archived may be archived, but a procedure that excludes electronic data that is unnecessary for the user and archives the electronic data may be included. For example, the archive module 13 is provided with a machine learning engine that discriminates a pin pocket of a photograph or a photograph having substantially the same subject (photograph having substantially the same subject and composition) by machine learning, and image data as electronic data that has not been archived. When archiving, it is advisable to use a machine learning engine to automatically exclude out-of-focus photos and image data related to substantially the same photo, and select other image data for archiving. Further, for example, the archive module 13 may make the user confirm whether or not there is electronic data to be excluded from the archive before executing the archive process. In this case, in S132, the archive module 13 transmits information indicating unprocessed electronic data to the user terminal 30 and displays a confirmation screen on the user terminal 30 before executing the archive process. FIG. 6 is a flowchart of a procedure for asking the user to confirm in the archive process S132. As shown in FIG. 6, the archive module 13 transmits information (file name, thumbnail, etc. of electronic data) indicating electronic data that has not been archived to the user terminal 30 to notify the user terminal 30 (S1321). In S1321, the archive module 13 transmits a notification message to the user terminal 30 who is signed in with the usage ID determined that the archive process needs to be performed in S131. When the user terminal 30 receives the notification message (S1332), the user terminal 30 displays a confirmation screen including information (file name, thumbnail, etc.) of unprocessed electronic data indicated by the notification message (S1333). The confirmation screen includes a GUI (graphical user interface) and accepts a selection operation by a user who selects electronic data to be excluded from the archive (S1324). The user terminal 30 transmits a reply message indicating the selection result received in S1324 to the electronic data management server 10 (S1325). The archive module 13 receives the reply message from the user terminal 30 (S1326), identifies the electronic data indicated by the selection result included in the reply message, and archives the archived unprocessed electronic data excluding this electronic data (S1326). S1327).

The upload module 32 may upload all the electronic data generated by the user, but may exclude the electronic data unnecessary for the user and upload the data. For example, the upload module 32 temporarily stores the electronic data in the storage medium 31 in response to the generation of the electronic data, and also accepts and uploads a selection operation for selecting whether to upload to the user through the GUI. It is advisable to upload the electronic data only when the selection operation to that effect is accepted. FIG. 11 shows, as an example, an example of the GUI 60 displayed on the user terminal 30 in response to the generation of electronic data (image data) by taking a picture with the camera provided in the user terminal 30. The GUI 60 includes a preview 61 of image data generated by taking a picture with a camera. The GUI 60 includes a dialog 62 for confirming the user's upload intention together with the preview 61. The dialog 62 includes the GUI element 62a and the GUI element 62b, and accepts a selection operation for selecting the GUI element 62a or a selection operation for selecting the GUI element 62b. When the upload module 32 receives the selection element for selecting the GUI element 62a, the upload module 32 uploads the image data displayed in the preview 61 in response to the selection element, and receives the selection element for selecting the GUI element 62b. Image data is not uploaded. For example, when uploading electronic data on a regular basis (for example, on the first day of every month), the upload module 32 accepts a selection operation of selecting electronic data to be excluded from uploading to the user through the GUI, and only electronic data that is not excluded. Is read from the storage medium 31 and uploaded. As an example, FIG. 12 shows an example of the GUI 70 displayed on the user terminal 30 when electronic data (image data) generated by taking a picture with a camera provided on the user terminal 30 is periodically uploaded. The GUI 70 includes a photo list display 71. The photo list display 71 displays a list of image data stored in the storage medium 31 so that it can be individually selected by, for example, an icon or a thumbnail, and accepts a selection operation for selecting arbitrary image data. The GUI 70 includes a GUI element 72 that is selected following a selection operation for selecting image data in the photo list display 71. When the GUI element 72 is selected, the upload module 32 reads the image data excluding the image data selected in the photo list display 71 from the storage medium 31 and executes uploading. In the photo list display 71, instead of selecting the image data to be excluded from uploading, on the contrary, a selection operation for selecting the image data to be uploaded may be accepted. In this case, the upload module 32 is the GUI element 72. In response to the selection of, the image data selected in the photo list display 71 is read from the storage medium 31 and uploaded.

(Archive processing: second aspect)
Here, the archive process according to the second aspect executed by the archive module 13 will be described. In the archive process according to the second aspect, the user terminal 30 confirms the archive conditions and determines whether or not the archive process is necessary. According to the second aspect, the upload module 32 determines whether to archive the electronic data stored in the storage medium 31 with reference to the archive condition 50d, and uploads the electronic data each time a positive determination is made. To execute. FIG. 6 is a diagram schematically showing the configuration of the upload module 32 according to the first aspect. As shown in FIG. 6, the upload module 32 has a determination process S321 and an upload process S322. In the determination process S321, whether or not to upload the electronic data stored in the storage medium 31 to the electronic data management server 10 and archive it with reference to the archive condition (50d) corresponding to the own usage ID (50a). To judge. The upload module 32 refers to its own archive condition (50d) in response to storing new electronic data (for example, in response to generating image data by taking a picture with a camera) and makes a determination. Process S321 may be executed. The upload module 32 may execute the determination process S321 periodically (for example, at a fixed time every day) with reference to the archive condition (50d). When the determination process S321 determines that archiving is necessary, the upload module 32 uploads the electronic data stored in the storage medium 31 to the electronic data management server 10 via the channel C1 (S322). In the upload process S322, the upload module 32 adds meta information (flags, tags, etc.) indicating that it is "archived" to the uploaded electronic data. Meta information is added, for example, in file units of electronic data. As a result, each time the upload module 32 executes the upload process S322, the upload process executes the upload process by selecting only the electronic data (electronic data that has not been uploaded in the past) to which the "archived" meta information is not added. can do. Further, also in the determination process S321, the determination process can be performed only on the electronic data (electronic data that has not been uploaded in the past and has not been archived) to which the "archived" meta information is not added. The upload module 32 uploads electronic data together with the usage ID (50a) held in the user terminal 30. More preferably, the upload module 32 uploads electronic data together with the usage ID (50a), name information (50b), and address information (50c). More preferably, when the electronic data is grouped and stored in the storage medium 31, the upload module 32 uploads the electronic data together with the information of the name (tag name, folder name, etc.) indicating the group.

A specific example of the determination process S321 and the archive process S322 when the archive condition is a temporal rule is shown. In the determination process S321, the upload module 32 acquires the current date and time from, for example, the hardware clock or the system clock, and determines whether or not it is time to archive. For example, when the archiving condition indicates "Archive once a month on the 1st day", it is determined that archiving (uploading) is necessary when the current date is the 1st day of a certain month. For example, if the archiving condition is "Archive one month after the last archive", then the current date of acquisition is one month after the last archive (upload). , Determines that archiving is needed. In the archive process S322, only the electronic data to which the "archived" meta information is not added is selected from the electronic data in the storage medium 31 and the upload process is executed. As a result, the upload process S322 is executed every time the time indicated by the archive condition comes and the determination process S321 determines that archiving is necessary. At this time, the electronic data that has not been archived (that is, the previous one) The electronic data that has been determined in the determination process S321 and increased after the upload process) can be newly uploaded.

A specific example of the determination process S321 and the archive process S322 when the archive condition is a capacity rule is shown. In the determination process S321, the upload module 32 derives the capacity of the stored electronic data of the electronic data to which the "archived" meta information is not added, and sets the capacity (threshold value) as a condition for archiving. By comparison, it is determined that archiving is necessary if there is a match or excess. That is, the amount of electronic data that has increased since the previous archive (upload) is derived and determined. For example, when the archive condition indicates "10 GB" and the capacity of the derived unprocessed archived electronic data is 10 GB or more, it is determined that archiving is necessary. The upload module 32 may execute the determination process S321 on the electronic data at predetermined date and time (for example, 1:00 am every day) determined in advance with reference to the hardware clock or the system clock, for example. , The determination process S321 may be executed every time the electronic data is newly stored in the storage medium 31. In the upload process S322, the upload process is executed for the electronic data whose capacity is derived in the determination process S321 (that is, the archived unprocessed electronic data to which the "archived" meta information is not added in the storage area). do.

A specific example of the determination process S321 and the archive process S322 when the archive condition is a quantitative rule is shown. In the determination process S321, the upload module 32 is a condition for deriving and archiving the quantity (for example, the number of files) of the stored electronic data to which the "archived" meta information is not added. Compared to the existing quantity (threshold), if it matches or exceeds, it is determined that archiving is necessary. That is, the number of electronic data files that has increased since the previous archive (upload) is derived and determined. For example, when the archive condition indicates "100 pieces", and the quantity of the derived unprocessed archived electronic data is 100 pieces or more, it is determined that archiving is necessary. The upload module 32 may execute the determination process S321 on the electronic data at predetermined date and time (for example, 1:00 am every day) determined in advance with reference to the hardware clock or the system clock, for example. The determination process S321 may be executed every time the electronic data is newly stored in the storage medium 31. In the upload process S322, the upload process is executed for the electronic data whose quantity is derived in the determination process S321 (that is, the archived unprocessed electronic data to which the "archived" meta information is not added in the storage area). do.

In the upload process S322, the upload module 32 may upload all the electronic data that has not been archived (unuploaded), but may exclude the electronic data that is unnecessary for the user and upload it. For example, the upload module 32 presents the user the unprocessed archived electronic data in the storage medium 31 specified as to be uploaded after the determination process S321, and selects the electronic data to be excluded from uploading to the user through the GUI. It is advisable to accept operations and upload only unarchived electronic data that has not been excluded. As an example, FIG. 13 shows an example of the GUI 80 displayed on the user terminal 30 when the electronic data (image data) generated by taking a picture with the camera provided on the user terminal 30 is uploaded. The GUI 80 includes a photo list display 81. The photo list display 81 displays a list of unprocessed (unuploaded) image data stored in the storage medium 31 so that they can be individually selected by, for example, icons or thumbnails, and performs a selection operation to select arbitrary image data. accept. The GUI 80 includes a GUI element 82 that is selected following a selection operation for selecting image data in the photo list display 81. When the GUI element 82 is selected, the upload module 32 reads the image data that has not been archived, excluding the image data selected in the photo list display 81, from the storage medium 31 and executes uploading. .. In the photo list display 81, instead of selecting the image data to be excluded from uploading, on the contrary, the selection operation of selecting the image data to be uploaded may be accepted. In this case, the upload module 32 has the GUI element 82. In response to the selection of, the image data selected in the photo list display 81 is read from the storage medium 31 and uploaded.

In the upload process S322, all the electronic data that has not been archived (unuploaded) may be uploaded, but may include a procedure that excludes the electronic data that is unnecessary for the user and performs the upload process. For example, the upload module 32 is provided with a machine learning engine that discriminates between photo pinpoke and substantially the same photo (photos having substantially the same subject and composition) by machine learning, and image data as archive-unprocessed electronic data. When uploading, it is advisable to use a machine learning engine to automatically exclude out-of-focus photos and image data related to substantially the same photo, and select other image data for upload processing.

In the archive process according to the second aspect, the archive module 13 performs an archive process on the electronic data uploaded from the user terminal 30 in S322 without executing the determination process (S131) (S132). In S132, the archive module 13 identifies the usage ID attached to the uploaded electronic data, saves the electronic data in the storage area on the database 11 assigned to the usage ID, and for the saved electronic data. Archive processing may be performed. As an example, the archiving process includes storing electronic data in a physically portable storage medium such as a CD-R, DVD-R, USB memory, or SD card, and shipping the storage medium to a user. As an example, the archiving process includes sending a printed matter (photograph) on which the image data is printed to the user when the electronic data is image data (photograph data). As an example, in the archive process, when the electronic data is image data (photo data), a plurality of image data are arranged in a predetermined layout and printed to create a photo book, and the photo book is sent to the user. include. The shipping includes referring to the name information (50b) and the address information (50c) associated with the usage ID (50a), and shipping to the destination including the name and address. The archive module 13 may delete the electronic data that has completed the archive process from the storage area.

(Details of archiving process)
FIG. 8-1 shows a detailed process in the case of storing electronic data in a physically portable storage medium in the archive process (S132) according to the first aspect or the second aspect. The electronic data management server 10 has a device that accepts the insertion of the storage medium, and recognizes that the portable storage medium has been inserted (S132a). For example, the electronic data management server 10 includes a drive for reading and writing a CD-R or a DVD-R, and recognizes that the CD-R or the DVD-R has been inserted into the drive in S132a. For example, the electronic data management server 10 includes a USB interface that receives the insertion of the USB memory, and recognizes that the USB memory has been inserted into the USB interface. For example, the electronic data management server 10 includes an interface that accepts the insertion of an SD card, and recognizes that the SD card has been inserted into the interface. Next, in the archive process (S132), the electronic data to be archived is read from the database 11 and stored in the storage medium (S132c). In S132c, the electronic data of the database 11 may be copied to the storage medium. Further, in S132c, the electronic data read from the database 11 may be authored in a specific format and written to the storage medium. For example, when the electronic data is an image data (photo data) such as PEG format or PNG format, or a video data file such as MPEG format or AVI format, the DVD-Video format or BDMV (BDMV) specified in the DVD Forum is used. It is advisable to author in the Blu-ray Disc Movie format and write it to a DVD disc (DVD-R or the like) or a Blu-ray disc (BD-R or the like). Further, the archive process (S132) includes a step of generating and printing a label that identifies the storage medium in which the electronic data is written in S132c (S132d). The label may be a label attached directly to the storage medium, or may be a label attached to the packing box in which the storage medium is packed. An example of a label is a disk-shaped label attached to the surface of a DVD-R or BD-R, which is a storage medium. An example of a label is a label attached to a housing of a USB memory which is a storage medium. An example of a label is a label attached to a carton box in which a storage medium is packed. In S132d, when the electronic data written in the storage medium in S132c are grouped, a label printed with characters including a name (tag name, folder name, etc.) indicating the group is generated. That is, characters including the group name (tag name, folder name, etc.) when grouped on the database 11 or the group name (tag name, folder name, etc.) attached to the electronic data in the upload process S322 are input. Generate a printed label. For example, specifically, the archive module 13 prints characters including a name indicating a group (tag name, folder name, etc.) on a printer connected to the electronic data management server 10 and having a label set. The print instruction is sent, and the label printed by the printer is printed.

FIG. 8-2 shows a detailed process in the case of creating a photo book from electronic data which is image data (photograph data) in the archive process (S132) according to the first aspect or the second aspect. As shown in FIG. 5, the archive module 13 holds a layout template 13a for a photo book. The layout template 13a is template data in which a photo layout for creating a photo book is defined, and includes layout information such as how many photos are arranged per page of the photo book. The archive module 13 reads out the layout template 13a (S132e). When a plurality of layout templates 13a are held, the archive module 13 selects and reads one layout template 13a according to the selection from the user (S132e). Next, in the archive process (S132), the electronic data to be archived is applied to the read layout template 13a and edited to create a photo book (S132 g). Further, in S132g, editing is performed by inserting characters for identifying the photo book into a predetermined page of the photo book. For example, in S132g, characters for identifying the photo book are laid out on the front cover, spine cover, and / or each page of the photo book. The characters for identifying the photo book are, for example, characters including a name (tag name, folder name, etc.) indicating the group when the electronic data used in S132g is grouped. That is, characters including the group name (tag name, folder name, etc.) when grouped on the database 11 or the group name (tag name, folder name, etc.) attached to the electronic data in the upload process S322. be. Electronically created photobooks are printed and bound. The archive module 13 executes a process of printing the created photo book (S132h). In S132h, the archive module 13 transmits a print instruction to print each page of the photobook completed in S132g to the printer connected to the electronic data management server 10, and each page of the photobook is printed from the printer. Will be done. Each page of the printed photo book is bound by the user (worker, operator) of the electronic data management server 10, and finally the physical photo book is completed.

The storage media (S132a to S132c) and photobooks (S132e to S132h) physically generated by the archiving process are shipped to the user. That is, the storage medium and the photo book are packed in a packing material such as an envelope or a cardboard box, and a shipping label with the address of the user who is the shipping destination is attached to the packing material and shipped to the user via the shipping company. Will be done. The archive process (S132) includes a printing process for printing the user's address on the shipping label. FIG. 8-3 shows a detailed process for printing on the shipping label in the archive process (S132). The archive module 13 refers to the name information 50b and the address information 50c of the user information 50, specifies the name and address indicated by the name information 50b and the address information 50c (S132p), and prints the specified name and address on the shipping label. And print (S132q). That is, the archive module 13 refers to the user information 50 stored in the electronic data management server 10, or refers to the name information 50b and the address information 50c sent in the upload process S322, and refers to the name and address. To identify. In S132q, the archive module 13 transmits a print instruction to print and print the characters of the name and address specified in S132p to the printer connected to the electronic data management server 10 and set with the shipping label. The printer prints a shipping label with your name and address printed on it. The shipping label may be a courier invoice (slip) provided by the shipping company, a sticker-like label that can be attached to an envelope, or the like.

As described above, the electronic data management server 10 provides online storage for storing and managing the user's electronic data uploaded from the user terminal 30, and is automatically stored in a physical storage medium or photobook by the archive module 13. It is possible to provide a service that archives electronic data and delivers it to users.
(Erase of electronic data)

The electronic data management server 10 includes an erasing module 14. The erasing module 14 is a functional element including a computer program. The erasing module 14 performs a process of erasing the electronic data in the database 11 according to a predetermined condition. The details of the processing of the erasing module 14 will be described later. Similarly, the user terminal 30 includes an erasing module 33. The erasing module 33 is a functional element that includes a computer program. The erasing module 33 performs a process of erasing the electronic data in the storage medium 31 according to a predetermined condition.

From here, the "electronic data end-of-life service" using the life-and-death information management server 20 will be described. The life-and-death information management server 20 is a server that manages user information (user information 21) corresponding to the usage ID registered in the user information 50. An example of user information 21 is a user's name, address, contact information, life / death information, and the like. The life-and-death information management server 20 is a server operated by a business entity such as a company, and manages user information 21 of the user based on a contract individually concluded with the user. An example of the life-and-death information management server 20 is a server related to online banking operated by a financial institution such as a bank or a securities company, and with a user who is an account holder (for example, a bank depositor) of this financial institution. The user information 21 of the account holder is managed based on the contract. FIG. 9 is a diagram showing an example of user information 21. FIG. 9 shows an example of user information associated with the usage ID “USR001”. In the example shown in FIG. 9, in the user information 21, information indicating the usage ID "USR001" (21a), information indicating the user's name of the usage ID "USR001" (21b), and address information of the usage ID "USR001" (21c), information (21d) regarding the account balance of the user with the usage ID "USR001", and life / death information (21e) indicating whether or not the user with the usage ID "USR001" has died are associated with each other.

Of the user information 21, at least the life-and-death information 21e is manually updated by the operator 3, who is a person related to the business entity that operates the life-and-death information management server 20. The operator 3 is, for example, an employee of a business entity that operates the life-and-death information management server 20, an employee of a company entrusted to this business entity, and the like, and accesses and rewrites (updates) the user information 21. A person who has authority. Upon receiving a notification from the bereaved family of the user managed in the user information 21 that the user has died, the operator 3 accesses the user information 21 and updates the life / death information 21e of the user to the effect that the user has died. For example, the life-and-death information 21e indicates that the user is normally alive and the user's account can be used, and the user's account cannot be used because the user died due to the update by the operator 3. Indicates that.

The life-and-death information management server 20 includes a notification module 22. The notification module 22 is a functional element including a computer program. In response to the update of the life / death information 21e in the user information 21, the notification module 22 notifies the electronic data management server 10 or the user terminal 30 that the update (that is, the user has died). Perform the notification process. In the electronic data management server 10, in response to the notification from the notification module 22, the erasing module 14 performs a process of erasing the electronic data of the dead user stored in the database 11. In the user terminal 30, in response to the notification from the notification module 22, the erasing module 33 performs a process of erasing the electronic data of the dead user stored in the storage medium 31.

FIG. 10-1 is a flowchart showing an example of processing of the notification module 22 and the erasing module 14. When the life / death information 21e of a certain user is updated by the operator 3, the notification module 22 notifies the electronic data management server 10 of the update via the communication channel C3 (S221). In S221, the notification module 22 transmits a notification message to the electronic data management server 10 via a communication channel including the Internet and the like. The notification of S221 includes, for example, a usage ID (21a), a name (21b), and an address information (21c) corresponding to the updated life / death information 21e. When the erasing module 14 receives the notification (S141), in response to the notification, the user who has been notified of the death identifies the electronic data stored in the database 11 as the data to be erased (S142). In S142, the erasing module 14 specifies the electronic data stored in the storage area assigned to the usage ID (50a) on the user information 50 corresponding to the notified usage ID (21a) as the data to be erased. The erasing module 14 erases the electronic data specified in S142 from the database 11 (S143).

FIG. 10-2 is a flowchart showing an example of processing of the notification module 22 and the erasing module 33. When the life / death information 21e of a certain user is updated by the operator 3, the notification module 22 notifies the user terminal 30 of the update via the communication channel C2 (S222). In S222, the notification module 22 identifies the user terminal 30 signed in to the life / death information management server 20 by the usage ID (50a) corresponding to the usage ID (21a) whose life / death information 21e has been updated by the operator 3. A notification is transmitted to the user terminal 30. When the erasing module 33 receives the notification (S331), in response to this, the erasing module 33 identifies the electronic data in the storage medium 31 as data to be erased (S332), and erases the specified electronic data from the storage medium 31 (S331). S333).

As described above, by linking the erasing module 14 and the notification module 22, the electronic data stored in the electronic data management server 10 by the user is automatically erased when the user dies, and the bereaved family and others. It is possible to provide a so-called end-of-life service for electronic data that makes it visible to the public. In addition, by linking the erasing module 33 and the notification module 22, the electronic data stored in the user terminal 30 by the user is automatically erased in the wake of the death of the user, and is seen by the bereaved family and others. It is possible to provide a so-called end-of-life service for electronic data. Sensitive information about the life or death of a person is usually difficult for a third party to obtain, but it is linked with the update of user information (user information 21) of an institution such as a financial institution that is in a position to receive early notification of death from the bereaved family. Then, if the electronic data is erased, the electronic data can be erased at an early stage.
(Hardware configuration)

Next, an example of the hardware configuration of the electronic data management server 10, the life-and-death information management server 20, and the user terminal 30 will be described. The electronic data management server 10 is a computer device such as a personal computer or a workstation and has a web server function. The electronic data management server 10 includes a communication circuit, a memory, a processor, a storage, and the like, and these are connected by a bus. The communication circuit is a communication circuit that establishes a communication channel C1 with the user terminal 30 and a communication channel C3 with the life-and-death report management server 20, and includes, for example, a network board for making an Internet connection. The processor includes a processing unit such as a CPU and an MPU, and performs various controls on the electronic data management server 10 by reading and executing program instructions stored in the memory. The memory includes ROM and RAM, and holds data temporarily or permanently used by the processor, computer programs executed by the processor, and the like. In the present embodiment, data such as the user information 50 and the layout 13a are stored in the memory. Further, in the present embodiment, a computer program including a program instruction corresponding to S131 to S132, a program instruction corresponding to S141 to S143, and the like is held in the memory, and these program instructions are read and executed by the processor. As a result, the archive module 13 and the erase module 14 are realized. The storage includes a storage medium such as an HDD or SSD, and the database 11 is generated on the storage. The user information 50, the layout 13a, and the program instructions may be stored in the storage. Memory and storage may be integrated.

The life-and-death information management server 20 is a computer device such as a personal computer or a workstation. The life-and-death information management server 20 includes a communication circuit, a memory, a processor, a storage, an input device, and the like, and these are connected by a bus. The communication circuit is a communication circuit that establishes a communication channel C3 with the electronic data management server 10 and a communication channel C2 with the user terminal 30, and includes, for example, a network board for connecting to the Internet. The processor includes a processing unit such as a CPU and an MPU, and controls the life-and-death information management server 20 by reading and executing a program instruction stored in the memory. The memory includes ROM and RAM, and holds data temporarily or permanently used by the processor, computer programs executed by the processor, and the like. In the present embodiment, data such as user information 21 is stored in the memory. Further, in the present embodiment, the computer program including the program instructions corresponding to S221 and S222 is held in the memory, and the notification module 22 is realized by reading and executing these program instructions by the processor. The storage includes a storage medium such as an HDD or SSD. The user information 21 and the above program instructions may be stored in the storage. Memory and storage may be integrated. The input device includes an input device such as a keyboard, a mouse, and a touch panel, and accepts an input operation in which the operator 3 edits the user information 21.

The user terminal 30 is a computer device such as a personal computer, a smartphone, or a digital camera. The user terminal 30 includes a communication circuit, a memory, a processor, a storage, an input device, a display device, and the like, and these are connected by a bus. The communication circuit is a communication circuit that establishes a communication channel C1 with the electronic data management server 10 and a communication channel C2 with the life-and-death information management server 20, and includes, for example, a network board and a cellular communication circuit for connecting to the Internet. The processor includes a processing unit such as a CPU and an MPU, and performs various controls on the user terminal 30 by reading and executing a program instruction stored in the memory. The memory includes ROM and RAM, and holds data temporarily or permanently used by the processor, computer programs executed by the processor, and the like. In the present embodiment, data such as user information 50 is stored in the memory. Further, in the present embodiment, a computer including a program instruction corresponding to S321 to S322, a program instruction corresponding to S331 to S333, a program instruction corresponding to S1322 to S1325, a program instruction for displaying GUI60, 70, 80, and the like. The program is held in the memory, and the upload module 32 and the erase module 33 are realized by reading and executing these program instructions by the processor. The storage includes a storage medium such as an HDD or SSD. The storage includes electronic data generated by the user terminal 30 (for example, electronic data such as downloaded image data, and if the user terminal 30 is equipped with a camera, electronic data such as image data captured by the camera) and the like. ) Is stored and stored in the storage medium 31. In addition to the electronic data, the above program instructions may be stored in the storage. Memory and storage may be integrated. The input device includes an input device such as a keyboard, a mouse, and a touch panel, and accepts a user's input operation. In the present embodiment, the input device accepts the input of names (tag names, folder names, etc.) for grouping electronic data, the selection operation in S1324, the selection operation through GUI60, 70, 80, and the like. The display device includes a display such as a liquid crystal display or an organic EL display, and is controlled by a processor to display characters and graphics such as GUI60, 70, 80, and the like.

The computer program stored in the memory of the user terminal 30 may be an application pre-installed at the time of manufacture and sale of the user terminal 30, or may be arbitrarily downloaded by the user from an external app store via the Internet. It may be an installed application.

Although the embodiments of the present invention have been described above with reference to FIGS. 1 to 13, this is not limited but exemplary. It is clear that various modifications and changes can be made to embodiments without departing from the spirit of the invention as described in the claims.

10 Electronic data management system 11 Database 13 Archive module 14 Erase module 20 Life / death information management server 21 User information 22 Notification module 30 User terminal 31 Storage medium 32 Upload module 33 Erase module 50 User information

Claims (4)

A system that manages electronic data
Includes a cloud server to which a storage area for storing electronic data is allocated for each usage ID.
For each usage ID, the archiving condition, which is the condition for archiving electronic data, is retained.
It accepts uploads of electronic data from a user terminal signed in with a usage ID via the Internet, and saves the uploaded electronic data on the cloud server assigned to the usage ID of the user terminal that is the upload source. Save to area and
For each usage ID, it is determined whether or not the archive condition is satisfied, and if a positive determination is made, in response to this, the user ID is assigned to the usage ID determined to satisfy the archive condition. A system that automatically executes an archive process that archives electronic data stored in the storage area.
In the archive process, the portable storage medium in which the electronic data is written is delivered to the user corresponding to the usage ID, and the printed matter generated by printing the electronic data is delivered to the user corresponding to the usage ID. A system including one of the above and the delivery of a photobook generated by arranging electronic data according to a predetermined layout to a user corresponding to the usage ID. A system that manages electronic data
Includes an upload module held on a user terminal that has a storage area for storing electronic data
Preserve the archiving condition, which is the condition for archiving electronic data,
The upload module signs in to the cloud server with a usage ID via the Internet, and then signs in to the cloud server.
The upload module determines whether or not the archiving conditions are satisfied, and if a positive determination is made, the upload module automatically transmits the electronic data stored in the storage area to the cloud server in response to the positive determination. It is a system to upload to
The cloud server automatically executes an archiving process for archiving uploaded electronic data.
In the archive process, the portable storage medium in which the electronic data is written is delivered to the user corresponding to the usage ID, and the printed matter generated by printing the electronic data is delivered to the user corresponding to the usage ID. A system including one of the above and the delivery of a photobook generated by arranging electronic data according to a predetermined layout to a user corresponding to the usage ID. A system that manages electronic data
Notification module stored in the cloud server and
Equipped with an erasing module held in a user terminal that has a storage area for storing electronic data
The user information including the life / death information of the user indicated by the usage ID is stored in the cloud server in association with the usage ID.
When the user terminal is signed in to the cloud server by the usage ID via the Internet, the notification module responds when the life / death information is updated to information indicating death on the user information. Then, a notification indicating the update is automatically sent to the user terminal.
The erasing module is a system that automatically erases electronic data stored in the storage area upon receiving the notification. A system that manages electronic data
Notification module stored in the first cloud server,
It is equipped with an erasing module held in a second cloud server that has a storage area for storing electronic data for each usage ID.
The user information including the life / death information of the user indicated by the usage ID is stored in the first cloud server in association with the usage ID.
When the life / death information is updated to information indicating death on the user information, the notification module automatically sends a notification indicating the update to the second cloud server in response to the update via the Internet. death,
The erasing module is a system that receives the notification and automatically erases the electronic data stored in the storage area associated with the usage ID indicated by the notification.

Images