JP7328948B2 - Information processing device, information processing method, information processing program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

In the past, when sharing the created Shukatsu Note information, etc. with a specific reader, a third party designated by the creator of the Shukatsu Note before his death entered the death of the creator into the system, and the system sent the information to the specific reader. There is a service that automatically delivers information such as notes on final life. (For example, see Non-Patent Document 1)

SeeUAll Co., Ltd. HP, [online], searched on October 7, 2019, Internet <URL: https://cuall. net/index. php>

However, while the creator is alive, it is not possible to distribute information such as final notes to specific readers and share the contents, and the monk of the temple that has a relationship with the creator's family There was a problem that information such as Shukatsu notebook information could not be used during the lifetime of the producer as a material to know the character of the person.

SUMMARY OF THE INVENTION It is an object of the present invention to provide an information processing apparatus, an information processing method, and an information processing program capable of appropriately managing final life document data.

An information processing apparatus according to the present invention is an information processing apparatus that manages final activity document data, and includes a reception unit that accepts registration of final activity document data, a registration unit that registers the final activity document data in a database, and a registered a management unit for managing the final life document data, the reception unit receives designation of users who can view the final life document data, and the management unit allows users other than the designated users to view the final life document data. It is characterized by limiting

According to the present invention, it is possible to provide an information processing apparatus, an information processing method, and an information processing program capable of appropriately managing end-of-life document data.

It is a figure showing an example of a schematic structure of an information processing system concerning an embodiment. It is a figure which shows an example of the hardware constitutions of the server which concerns on embodiment. It is a figure which shows an example of the data memorize|stored in the memory|storage device of the server which concerns on embodiment. It is a figure which shows an example of the data memorize|stored in the memory|storage device of the server which concerns on embodiment. It is a figure which shows the blood relationship based on the relationship of the database shown in FIG.3(c). 5 is a diagram showing a tree structure of final activity documents based on the relationships of the database shown in FIG. 4; FIG. It is a figure showing an example of functional composition of a server concerning an embodiment. It is a figure which shows an example of the hardware structure and functional structure of the user terminal which concerns on embodiment. It is a figure which shows an example of the screen displayed on the display apparatus of the user terminal which concerns on embodiment. 7 is a flow chart of a final life notebook viewing process executed by the information processing system according to the embodiment when the viewer is an individual member of the parish family. 8 is a flowchart of a personal end-katsu note browsing function executed by the information processing system according to the embodiment; 10 is a flowchart of a process for viewing a final note, executed by the information processing system according to the embodiment, when the viewer is a monk of a family temple; 6 is a flow chart of a Shukatsu Note temple browsing function executed by the information processing system according to the embodiment; 10 is a flowchart of a parent-child relationship browsing process when going back to the parent direction, which is executed in the information processing system according to the embodiment; 10 is a flowchart of a parent-child relationship viewing process 1 in the case of proceeding forward in the child direction, which is executed by the information processing system according to the embodiment; 10 is a flowchart of a parent-child relationship viewing process 1 in the case of proceeding forward in the child direction, which is executed by the information processing system according to the embodiment; 10 is a flowchart of a parent-child relationship viewing process 2 in the case of proceeding forward in the child direction, which is executed by the information processing system according to the embodiment; 7 is a flowchart of a detailed display process of a family temple executed by the information processing system according to the embodiment; 6 is a flowchart of a grave detail display process executed by the information processing system according to the embodiment;

[Embodiment]
BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below with reference to the drawings. In the following explanation, ``parish family'', ``family temple'', ``burial mound'', and ``shukatsu document'' are explained as having the following meanings.
Danka: A house or believer who belongs to a specific temple and entrusts all funeral services to that temple and pays donations (dan means donation).
Bodaiji: A temple where mortuary tablets (of ancestors) have been enshrined for generations, devoting themselves to the temple's principles.
Tomb: A structure in which a corpse or remains are placed to mourn the deceased.
Shukatsu document: I want to record and pass on to my descendants, including records about the end of my life, about my upbringing, what made me happy in life, what I struggled with, and how I overcame it. A document that records all or part of what you think. Note that the final life document may include memorandum-like records such as information on the safe deposit box where inherited assets are deposited.

FIG. 1 is a diagram showing an example of a schematic configuration of an information processing system 1 according to an embodiment. First, the configuration of the information processing system 1 will be described with reference to FIG. The information processing system 1 includes a server 2 (information processing device) and a plurality of user terminals 3 connected to the server 2 via a network 4 . The number of servers 2 and user terminals 3 included in the information processing system 1 is arbitrary. Communication between the server 2 and the user terminal 3 may be wireless communication or wired communication.

(Server 2)
FIG. 2 is a diagram showing an example of the hardware configuration of the server 2 (information processing device). As shown in FIG. 2, the server 2 includes a communication IF 200A, a storage device 200B, a CPU 200C, and the like. The server 2 may be provided with an input device (for example, keyboard, touch panel, etc.) and a display device (for example, liquid crystal monitor, organic EL monitor, etc.).

Communication IF 200A is an interface for communicating with an external terminal (user terminal 3 in the embodiment).

The storage device 200B is, for example, an HDD or a semiconductor storage device. The storage device 200B stores information processing programs and various databases (hereinafter also referred to as DBs) used by the server 2 . In this embodiment, the information processing program and various DBs are stored in the storage device 200B of the server 2, but an external storage device such as a USB memory or an external server (data server) connected via the network 4 may be stored. , and can be referred to or downloaded as needed.

For example, the storage device 200B stores parishioner DB 1, temple DB 2, tomb DB 3, user DB 4, final life document DB 5, and the like.

FIG. 3 is a diagram showing an example of information (data) stored in each of DB1 to DB5. In this embodiment, a plurality of DBs are provided, but one DB may be stored in the storage device 200B. Also, it does not necessarily have to be stored as a DB in the storage device 200B. Also, how the information (data) of each DB is associated and stored in the storage device 200B is arbitrary.

(Danka DB1)
As shown in FIG. 3A, the parishioner DB 1 is a DB in which information such as parishioner IDs, temple IDs, tomb IDs, tomb section IDs, and representative user IDs are associated with the parishioner ID. . In this embodiment, the server 2 manages data about parishioners in the parishioner DB1.

(Temple DB2)
As shown in FIG. 3B, the temple DB 2 is a DB in which the temple ID is associated with information such as the ID of the parent temple, the name of the temple, the address of the temple, the telephone number, and the e-mail address. In this embodiment, the server 2 manages data on temples in the temple DB 2 .

(Tomb DB3)
As shown in FIG. 3(c), the tomb DB 3 is a DB in which information such as the ID of the parent tomb, the name of the cemetery in which the burial is located, the address of the cemetery, the telephone number, and the e-mail address is associated with the tomb ID. In this embodiment, the server 2 manages the data regarding the tomb in the tomb DB3.

(User DB 4)
As shown in FIG. 3(d), the user DB 4 includes personal IDs (user IDs), passwords, affiliated parishioner IDs, temple IDs, father's personal IDs, mother's personal IDs, birth order, spouse's personal IDs, and passwords. It is a DB in which information such as ID (if there is a spouse), type of life (living or dead), gender, name, address, telephone number, email address, etc. is associated. In this embodiment, the server 2 manages in the user DB 4 data on individuals belonging to parishioners and data on individual priests belonging to temples.

(End of life document DB5)
As shown in FIG. 4, the final activity document DB 5 contains the ID of the chapter (unit) that constitutes the final activity document, the ID of the individual who is the producer (author) of the chapter, the ID of the next chapter, the child chapter ID of the individual user who can view the document data of the chapter (disclosure destination personal ID), permission to view the family temple of the user who is the creator (author) of the chapter, permission to view the document data of the chapter It is a DB in which various disclosure times (for example, before death (still alive) or after death (already dead)), chapter titles, chapter text data, etc. are associated with each other. In this embodiment, the server 2 manages in the final activity document DB 5 data related to final activity notes created by individuals belonging to parishioners. In the present embodiment, as shown in FIG. 4, when a user (individual) belonging to a parishioner creates a final life document, the creator determines whether the individual who can view the final life document, whether the priest of the family temple can view it, You can specify for each chapter of the final life document that it can be viewed after the creator passes away. The server 2 sets the specified contents for each chapter, and stores the settings in the final life document DB 5. - 特許庁

FIG. 5 is a diagram showing blood relations of parishioners based on the relationships in the user DB 4 shown in FIG. 3(d). The relationship shown in FIG. 5 is shown from the father, mother, birth order, and spouse relationship of the user DB 4 shown in FIG. 3(d). In FIG. 5, there are nodes whose names are indicated by *** to ***, but this is because names are not exemplified in the user DB 4 shown in FIG. 3(d).

FIG. 6 is a diagram showing a tree structure of final activity documents based on the relationships in the final activity document DB 5 shown in FIG. The tree structure of the final activity document shown in FIG. 6 is shown from the relationship between the chapter, sub-chapter and next chapter of the final activity document DB 5 shown in FIG.

The CPU 200C controls the server 2 and includes ROM (Read Only Memory) and RAM (Random Access Memory) not shown.

FIG. 7 is a diagram showing an example of the functional configuration of the server 2 according to the embodiment. As shown in FIG. 7, the server 2 has functions such as a receiving section 201 (accepting section), a transmitting section 202 (output section), a registering section 203, a managing section 204, an authenticating section 205, and the like. Note that the functions shown in FIG. 7 are realized by the CPU 200C executing an information processing program stored in the server 2. FIG.

The receiving unit 201 receives data transmitted from the user terminal 3 via the network 4 . For example, the receiving unit 201 receives (accepts) the following data. Note that the data illustrated below is merely an example of data received by the receiving unit 201, and the data received by the receiving unit 201 is not limited to the data illustrated below.
(1) Life and death document data (2) Designation of users who can view life and death document data (3) Designation of time when life and death document data can be viewed (4) Change of life and death of creator of life and death document data ( 5) Information on the family temple to which the creator of the final life document data belongs and information on the cemetery where the creator is buried

Note that the receiving unit 201 receives designation of a user who can view the final activity document data for each unit constituting the final activity document data. Further, the receiving unit 201 receives designation of a period when the final activity document data can be browsed for each unit constituting the final activity document data. In addition, the receiving unit 201 receives designation of users who can view the final life document data in group units.

The transmission unit 202 transmits (outputs) data to the user terminal 3 via the network 4 . For example, the transmission unit 202 transmits to the user terminal 3 the end-of-life document data requested for viewing.

The registration unit 203 controls the storage device 200B and registers data in each DB of the storage device 200B. For example, the registering unit 203 registers the final activity document data received by the receiving unit 201 in the final activity document DB 5 of the storage device 200B. Also, for example, the registration unit 203 registers at least one of the family temple information and the graveyard information received by the reception unit 201 in at least one of the temple DB2 and the tomb DB3 of the storage device 200B.

The management unit 204 manages the final activity document data registered in the final activity document DB 5 . For example, the management unit 204 restricts viewing of the end-of-life document data by a user other than a designated user. Also, for example, the management unit 204 restricts viewing of the end-of-life document data outside of the specified period. Also, for example, the management unit 204 restricts viewing of the final life document data by users who are classified outside the specified group. Also, for example, the management unit 204 changes the life or death of the creator of the final life document data when the user is classified into a group in which life or death can be changed.
In this embodiment, the management unit 204 "restricts" browsing of the final life document data by users other than the specified user or users classified into the specified group. The configuration may be such that viewing of the end-of-life document data of a designated user or a user classified into a designated group is "permitted" (possible).
In addition, the management unit 204 “restricts” browsing of the end-of-life document data outside the specified period, but the management unit 204 “permits” (allows) browsing of the end-of-life document data in the specified period. ) may be used.

The authentication unit 205 authenticates the login ID and password (PW) of the user accessing the server 2 . For example, in the present embodiment, when using the information processing system 1, a user who is an individual parishioner or a monk of a temple enters a login ID and password on a login screen displayed on the user terminal 3, which will be described later, and enters the login ID and password into the server 2. User authentication processing executed by the authentication unit 205 is performed.

The entered login ID and password are transmitted to the server 2 via the network 4 . The server 2 confirms whether the set of the login ID and password received by the receiving unit 201 matches the set of the personal ID and password in the user DB 4 .

Here, the login ID may be realized by using an e-mail address instead of a personal ID. It may be realized by adding processing of factor authentication. When user authentication succeeds in identity verification, the personal ID of the current user is determined, and the authentication unit 205 identifies a record in the user DB 4 in which the value of the personal ID matches the value of the determined personal ID. Then, if the parishioner ID of the identified record has a value, the determined personal ID is stored in the storage device of the server 2 as the personal ID of the parishioner, otherwise as the personal ID of the monk of the family temple ( It may be stored in a server-side cookie used for managing a communication session with a web browser).

(User terminal 3)
FIG. 8 is a diagram showing an example of the hardware configuration and functional configuration of the user terminal 3 according to the embodiment. FIG. 8(a) is a diagram showing an example of the hardware configuration of the user terminal 3, and FIG. 8(b) is a diagram showing an example of the functional configuration of the user terminal 3. As shown in FIG. The user terminal 3 is a PC (Personal Computer), a mobile terminal (for example, a tablet terminal), or the like. As shown in FIG. 8A, the user terminal 3 includes a communication IF 300A, a storage device 300B, an input device 300C, a display device 300D, a CPU 300E, and the like.

Communication IF 300A is an interface for communicating with another device (server 2 in the embodiment).

The storage device 300B is, for example, a HDD (Hard Disk Drive) or a semiconductor storage device (SSD (Solid State Drive)). The storage device 300B stores an identifier (ID) of the user terminal 3, an information processing program, and the like. The identifier may be newly assigned to the user terminal 3 by the server 2, or may be an IP (Internet Protocol) address, MAC (Media Access Control) address, or the like.

The input device 300C is, for example, a keyboard, a touch panel, or the like, and the user operates the input device 300C to input data necessary for using the information processing system 1 or to request viewing of final life document data. can be done.

The display device 300D is, for example, a liquid crystal monitor or an organic EL monitor. The display device 300</b>D displays screens necessary for using the information processing system 1 .

The CPU 300E controls the user terminal 3 and has ROM and RAM (not shown).

As shown in FIG. 8B, the user terminal 3 has functions such as a receiving section 301, a transmitting section 302, a storage device control section 303, an operation receiving section 304, a display device control section 305, and the like. Note that the function shown in FIG. 8B is implemented by the CPU 300E executing the information processing program stored in the storage device 300B.

The receiving unit 301 receives data transmitted from the server 2 .

The transmission unit 302 assigns an identifier to data input using the input device 300C and transmits the data to the server 2 . By assigning an identifier to the data transmitted from the user terminal 3, the server 2 can recognize from which user terminal 3 the received data is transmitted.

The storage device control unit 303 controls the storage device 300B. Specifically, the storage device control unit 303 controls the storage device 300B to write and read data.

The operation reception unit 304 receives an input operation on the input device 300C.

The display device control unit 305 controls the display device 300D. Specifically, the display device control unit 305 controls the display device 300D to display a screen necessary for using the information processing system 1 according to the embodiment.

Note that the user terminal 3 may use, for example, a WEB browser to display data transmitted from the server 2, and application software (hereinafter simply referred to as an application) may be installed in the user terminal 3. The data sent from the server 2 may be displayed on this application.

(Example of display screen)
FIG. 9 is a diagram showing an example of a screen displayed on the display device 300D of the user terminal 3 according to the embodiment. An example of a screen displayed on the display device 300D of the user terminal 3 according to the embodiment will be described below with reference to FIG. Note that the screen shown in FIG. 9 is merely an example, and other display modes may be used.

A screen G1 shown in FIG. 9A and a screen G2 shown in FIG. 9B are screens for displaying the parent-child relationship (parent-child relationship display screen). When moving to the screen G2 of , the screen transition is for going backward in the parent direction, and when moving from the screen G2 in FIG. 9B to the screen G1 in FIG. 9A, the screen transition is for going forward in the child direction. becomes. The screens G1 and G2 each have two areas, a parent area 1102 and a child area 1103 . Also, the parent area 1102 has a father area 1104 as a father node and a mother area 1105 as a mother node. The child area 1103 has child areas 1106 and 1107 corresponding to the number of children whose father is the person indicated by the father area 1104 and whose mother is the person indicated by the mother area 1105 . All areas also have a detail display button 1108 .

The initial display of the screen G1 has a configuration in which users who have passed user authentication are placed in the child area 1103. In terms of the screen G1, the screen G1 is displayed after "Miku Yamada" or "Taichi Yamada" in the child area 1103 logs in. shows the initial state. This is based on the fact that there can be unmarried or childless individuals, but there must be parents who gave birth to them.

Also, when an area of the parent area 1102, for example, the father area 1104 with the name "Taro Yamada" is selected (for example, by clicking) on the screen G1, the selected area is arranged in the child area 1103, and the selected area is displayed. 1110 and 1111, that is, ``Yamada Hajime'' 1110 and ``Yamada Hana'' 1111 are arranged in the parent area 1102, and the kinship relationship going back to the parent direction is displayed.

Conversely, when displaying prograde kinship relationships in the child direction, if an area in the child area 1103 on the screen G2, for example, the child area 1112 with the name "Taro Yamada" is selected (for example, by clicking), , if the selected area has a spouse, the spouse is placed in the parent area 1102; if the selected area has a child, the child is placed in the child area 1103; Anterograde kinship is displayed.

A screen G3 shown in FIG. 9C is a screen transition of personal related information display, and processing is executed by a web browser or an application as a menu display. When the user clicks the detail display button 1108 in the father area 1104 of the parent-child relationship display screen 1101 displayed on the screen G3, the screen G3 is displayed with a detailed menu 1052 displayed.

When the user clicks on the final life document in the detailed menu 1052 displayed on the display device 300D, the personal ID of the individual displayed in the father area 1104 is set as the creator's personal ID: α, and the final life document is viewed on the server 2. , and the server 2 that receives the request will use a server-side cookie used to manage the communication session with the Web browser. Executes the viewing process of the final life document when the viewer is an individual, with the personal ID as the personal ID of the viewer: β and the personal ID of the creator: α, and the personal ID is stored as that of the monk of the family temple. In this case, the individual ID is set as the browsing monk personal ID: γ, and together with the producer's personal ID: α, the reading process of the final life document is executed in the case where the browsing person is a monk of the family temple.

(Processing executed by information processing system 1)
10 to 18 are flowcharts showing an example of processing executed by the information processing system 1. FIG. Processing executed in the information processing system 1 will be described below with reference to FIGS. 10 to 18. The same components as those described with reference to FIGS. 1 to 9 are denoted by the same reference numerals. We omit redundant explanations.

FIG. 10 is a flow chart of the end-of-life document viewing process executed by the information processing system 1 according to the present embodiment when the viewer is an individual. In the following description, α is the personal ID of the creator of the final life document, and β is the personal ID of the user who makes the viewing request (also referred to as the viewing user).

(Step S101)
The viewing user operates the input device 300C of the user terminal 3 to perform a login operation. Specifically, the browsing user inputs his or her login ID and PW by operating the input device 300C. The input login ID and PW are transmitted from the transmitting section 302 of the user terminal 3 to the server 2 and received by the receiving section 201 of the server 2 . The authentication unit 205 of the server 2 authenticates the login ID and PW sent from the user terminal 3 . Specifically, the authentication unit 205 refers to the user DB 4 and authenticates the viewing user if the combination of the login ID and the PW transmitted from the user terminal 3 is registered. and PW are not registered, the browsing user is not authenticated.

(Step S102)
The viewing user operates the input device 300C of the user terminal 3 to request viewing of the end-of-life document. Specifically, the user operates the input device 300C of the user terminal 3 to input information that can identify the creator of the final life document requested to be viewed, such as personal ID and name. The browsing request is transmitted from the transmitting section 302 of the user terminal 3 to the server 2 and received by the receiving section 201 of the server 2 .

(Step S103)
The management unit 204 of the server 2 refers to the final activity document DB 5, specifies a record whose personal ID matches α, and acquires the value X of the chapter ID of the specified record. Here, as the personal ID, the personal ID of the creator of the final activity document is recorded only in the first chapter of the final activity document.

(Step S104)
The management unit 204 of the server 2 refers to the user DB 4, specifies a record whose personal ID value matches α, and acquires the life-and-death type value Y of the specified record.

(Step S105)
The server 2 calls the final life document personal viewing function. At this time, X obtained in step S103 is set as the value of the start chapter ID, the value Y obtained in step S104 is set as the value of the type of life or death, and the personal ID value β of the browsing user who is the browsing user is set as an argument. Call the active document individual viewing function. Processing by the final life document personal viewing function will be described later with reference to FIG. Here, the end-of-life document individual browsing function generates the end-of-life document data composed of the tree structure of FIG. This is a program function to be implemented in the server 2.

(Step S106)
The transmission unit 202 of the server 2 transmits (outputs) the viewing display data generated in step S<b>105 (hereinafter, viewing display data is also simply referred to as display data) to the user terminal 3 . The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

FIG. 11 is a flow chart of processing by the end-of-life document personal viewing function executed in the information processing system 1 according to the present embodiment.

(Step S201)
The final life document personal viewing function substitutes the value X of the starting chapter ID of the argument to the local variable next§ valid only within the function.

(Step S202)
The final activity document individual viewing function identifies a record in the final activity document DB 5 in which the value of the chapter ID matches the value of the local variable next§. It is determined whether or not a personal ID value is included. If the individual ID of the disclosure destination of the identified record includes the value of the individual ID of the viewing user, which is an argument (YES), the final life document individual viewing function executes the process of step S203. On the other hand, if the personal ID value of the viewing user is not included (NO), the final life document individual viewing function executes the process of step S206.

(Step S203)
The end-of-life document personal viewing function determines whether or not the disclosure time of the record in the end-of-life document DB 5 specified in step S202 is before death (still alive). If the document is still alive (YES), the final life document personal viewing function executes the process of step S205. If not during life (NO), the end-of-life document personal viewing function executes the process of step S204.

(Step S204)
The life-and-death document individual viewing function determines whether or not the value assigned to the life-and-death type argument is postmortem (already dead). If it is post-mortem (YES), the final activity document personal viewing function executes the process of step S205. If it is not after death (NO), the final life document personal viewing function executes the process of step S206.

(Step S205)
The final activity document individual viewing function is a final activity document that has the tree structure shown in FIG. The data is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a web browser). The data generated in this step is transmitted (output) to the user terminal 3 by the transmission unit 202 of the server 2 in step S106 of FIG.

(Step S206)
The final activity document individual viewing function determines whether or not the child chapter ID of the record in the final activity document DB 5 specified in step S202 is empty. If the sub-chapter ID of the record in the final activity document DB5 specified in step S202 is empty (YES), the final activity document individual browsing function executes the process of step S208. If the sub-chapter ID of the record in the final activity document DB 5 specified in step S202 is not empty (NO), the final activity document personal viewing function executes the process of step S207.

(Step S207)
The final activity document individual viewing function is the final activity document individual viewing function itself, the starting chapter ID value is the sub-chapter ID value confirmed in step S206, the life and death type value is the value when this function is called, and the viewing Recursively call the value of the user's personal ID as the value when this function is called.

(Step S208)
The end-of-life document individual viewing function determines whether the value of the next chapter ID of the record in the end-of-life document DB 5 specified in step S202 is equal to the start chapter ID of the argument. If it is equal to the start chapter ID of the argument (YES), the Shukatsu Kogyo Personal Viewing Function terminates the process (returns to the caller). If it is not equal to the start chapter ID of the argument (NO), the final life document personal viewing function executes the process of step S209.

(Step S209)
The final life document individual viewing function substitutes the value of the next chapter ID in step S208 for the local variable next§, and executes the process in step S202.

FIG. 12 is a flowchart of the final life document viewing process executed by the information processing system 1 according to the present embodiment when the viewer is a monk of the family temple. In the following description, α is the personal ID of the creator of the final life document, and γ is the personal ID of the monk of the family temple (hereinafter also referred to as the monk user) who makes the viewing request.

(Step S301)
A monk user operates the input device 300C of the user terminal 3 to perform a login operation. Specifically, the monk user operates the input device 300C to input his or her own login ID and PW. The input login ID and PW are transmitted from the transmitting section 302 of the user terminal 3 to the server 2 and received by the receiving section 201 of the server 2 . The authentication unit 205 of the server 2 authenticates the login ID and PW sent from the user terminal 3 . Specifically, the authentication unit 205 refers to the user DB 4 and authenticates the monk user if the combination of the login ID and PW transmitted from the user terminal 3 is registered. and PW combination is not registered, do not authenticate the monk user.

(Step S302)
The monk user operates the input device 300C of the user terminal 3 to request viewing of the final life document. Specifically, the user operates the input device 300C of the user terminal 3 to input information that can identify the creator of the final life document requested to be viewed, such as personal ID and name. The browsing request is transmitted from the transmitting section 302 of the user terminal 3 to the server 2 and received by the receiving section 201 of the server 2 .

(Step S303)
The management unit 204 of the server 2 refers to the user DB 4, specifies a record whose personal ID value matches α, and acquires the parishioner ID value D of the specified record.

(Step S304)
The management unit 204 of the server 2 specifies a record in the parishioner DB 1 in which the value of the parishioner ID matches D, and acquires the value G of the temple ID of the family temple of the specified record.

(Step S305)
The management unit 204 of the server 2 identifies a record in the user DB 4 in which the personal ID value matches γ, and acquires the temple ID value g of the identified record.

(Step S306)
The management unit 204 of the server 2 determines whether the value G acquired in step S304 and the value g acquired in step S305 are the same. If they are the same (YES), the management unit 204 executes the process of step S307. If not the same (NO), the management unit 204 terminates the process.

(Step S307)
The management unit 204 of the server 2 refers to the final activity document DB 5, specifies a record whose personal ID value matches α, and acquires the value X of the chapter ID of the specified record.

(Step S308)
The management unit 204 of the server 2 refers to the user DB 4, specifies a record whose personal ID value matches α, and acquires the life-and-death type value Y of the specified record.

(Step S309)
The management unit 204 of the server 2 calls the final life document personal viewing function. At this time, the management unit 204 calls the end-of-life document personal browsing function, using X obtained in step S307 as the value of the starting chapter ID and the value Y obtained in step S308 as the value of the type of life or death. The final activity document personal viewing function is managed by the final activity document DB 5, and the final activity document data composed of the tree structure in FIG. It is a program function to be implemented in the server 2, which is generated in a possible HTML format, etc.). Processing by the final life document personal viewing function will be described with reference to FIG.

(Step S310)
The transmission unit 202 of the server 2 transmits (outputs) the display data generated in step S309 to the user terminal 3 . The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

FIG. 13 is a flow chart of the Shukatsu Note temple viewing function executed by the information processing system 1 according to the present embodiment.

(Step S401)
The management unit 204 of the server 2 (finishing document personal browsing function) substitutes the value X of the starting chapter ID of the argument to the local variable next§ valid only within the function.

(Step S402)
The Shukatsu document temple browsing function refers to the Shukatsu document DB 5, specifies a record whose chapter ID value matches the value of the local variable next§, and determines whether or not the specified record can be browsed by the family temple. judge. If the specified record can be browsed to the family temple (YES), the final life document individual browsing function executes the process of step S403. On the other hand, if it is not possible to browse the family temple of the specified record (NO), the final life document individual browsing function executes the process of step S406.

(Step S403)
The final life document temple viewing function determines whether or not the disclosure time of the record in the final life document DB 5 specified in step S402 is before death (still alive). If the document is still alive (YES), the final life document personal viewing function executes the process of step S405. If it is not during life (NO), the end-of-life document personal viewing function executes the process of step S404.

(Step S404)
The final life document temple viewing function determines whether or not the value assigned to the life-and-death type argument is postmortem (already dead). If it is post-mortem (YES), the final activity document personal viewing function executes the process of step S405. If it is not after death (NO), the final life document individual viewing function executes the process of step S406.

(Step S405)
The final activity document individual viewing function is a final activity document that has the tree structure shown in FIG. The data is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a web browser). The data generated in this step is transmitted (output) to the user terminal 3 by the transmitting section 202 of the server 2 in step S310 of FIG.

(Step S406)
The final activity document individual viewing function determines whether or not the child chapter ID of the record in the final activity document DB 5 specified in step S402 is empty. If the sub-chapter ID of the record in the final activity document DB5 specified in step S402 is empty (YES), the final activity document individual viewing function executes the process of step S408. If the sub-chapter ID of the record in the final activity document DB5 specified in step S402 is not empty (NO), the final activity document individual viewing function executes the process of step S407.

(Step S407)
The final life document individual viewing function uses the final life document individual viewing function itself as the child chapter ID value confirmed in step S406 as the value of the start chapter ID and the value of the life or death type as the value when this function is called. Call recursively.

(Step S408)
The final activity document individual viewing function determines whether the value of the next chapter ID of the record in the final activity document DB 5 specified in step S402 is equal to the start chapter ID of the argument. If it is equal to the start chapter ID of the argument (YES), the Shukatsu Kogyo Personal Viewing Function terminates the process (returns to the caller). If it is not equal to the starting chapter ID of the argument (NO), the final life document personal browsing function executes the process of step S409.

(Step S409)
The final life document personal viewing function substitutes the value of the next chapter ID in step S408 for the local variable next§, and executes the processing in step S402.

In the above explanation with reference to FIG. 13, it was embodied whether or not an unspecified monk belonging to the family temple could view the final life document. Needless to say, it is possible to embody whether or not the document can be viewed by the user.

Also, an operation screen for changing the value of the type of life and death of a specific individual in the user DB 4 from before life (still alive) to after death (already dead) is logged in by a monk belonging to the family temple of the parish family to which the specific individual belongs. and display it when using the information processing system 1 according to the present invention, and not display it when a monk who does not belong to the family temple logs in and uses the information processing system 1 according to the present invention. The family temple in charge of the guru at the funeral can quickly implement the change from before death to after death, and it is possible to prevent a monk who has no connection with the family temple from taking charge of the specific individual's funeral.
Whether or not the monk belongs to the parishioner's family temple to which the specific individual belongs can be determined by the same process as steps S301 to S306 in FIG.

FIG. 14 is a flowchart of the parent-child relationship viewing process when going backward to the parent direction, which is executed by the information processing system 1 according to the embodiment. In the following description, the individual ID of an individual browsing the parent-child relationship or an individual in the father area 1104 or mother area 1105 of the parent area 1102 clicked is assumed to be α.

(Step S501)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches α, and sets the value X of the father's personal ID and the value Y of the mother's personal ID in the identified record. to get

(Step S502)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches X, and constructs the life/death type value, gender value, and name value of the identified record. The display data sandwiched between the tags of the rendered document is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a Web browser).

(Step S503)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches Y, and constructs the life/death type value, gender value, and name value of the identified record. The display data sandwiched between the tags of the rendered document is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a Web browser).

(Step S504)
The management unit 204 of the server 2 refers to the user DB 4 and extracts a group of records A={a, b, c, . .

(Step S505)
The management unit 204 of the server 2 acquires the value of life and death type, the value of the gender, and the value of the name for each record of the record group A={a, b, c, . . . } extracted from the user DB 4. is sandwiched between structured document tags in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed on a Web browser).

(Step S506)
The transmission unit 202 transmits (outputs) the display data generated in steps S502, S503, and S505 to the user terminal 3. FIG. The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

15A and 15B are flowcharts of the parent-child relationship browsing process in the case of proceeding forward in the child direction, which is executed by the information processing system 1 according to the embodiment. In this flowchart, the process branches because if the individual placed in the parent area 1102 of the screen G1 had children with multiple spouses in the past, which spouse This is to provide a procedure for allowing the user to select whether to display the parent-child relationship on the screen G1 in pairs. Also, in the following description, the individual ID of an individual viewing the parent-child relationship or an individual of the child area of the clicked child area 1103 is assumed to be α.

(Step S601)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches α, and determines whether or not the sex value of the identified record is male. If the gender value is male (YES), the management unit 204 executes the process of step S602. On the other hand, if the gender value is not male (NO), the management unit 204 executes the process of step S612 in FIG. 15B.

(Step S602)
The management unit 204 of the server 2 substitutes the value of α for the local variable f.

(Step S603)
The management unit 204 of the server 2 refers to the user DB 4 and extracts a record group P={a, b, c, .

(Step S604)
The management unit 204 of the server 2 deletes duplicate records from the extracted record group P={a, b, c, . …} is extracted.

(Step S605)
The management unit 204 of the server 2 determines that the number of records in the record group R={a, b, c, . It is determined whether there are 0 persons, 1 person, or otherwise. When the number of records is "0", the management unit 204 executes the process of step S606. When the number of records is "1", the management unit 204 executes the process of step S607. If the number of records is other than "0" and "1", that is, if it is 2 or more, the management unit 204 executes the process of step S611.

(Step S606)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches f, and acquires the spouse ID value m of the identified record. If the number of spouse records is 0 (the number of spouses is 0), the identified record group may be processed as element={} (empty set). In this case, for example, as the processing of the management unit 204, when processing each element, if the content (value) is empty when referring to it, it immediately returns (does not process the element). And it is sufficient. In other words, if an element exists, the element is processed based on a predetermined flow, but if the element does not exist, the element may be skipped without being processed.

(Step S607)
The management unit 204 of the server 2 acquires the personal ID value m of the mother of the record group R={a, b, c, . . . }.

(Step S608)
The management unit 204 of the server 2 refers to the user DB 4 and extracts a group of records A={a, b, c, .

(Step S609)
The management unit 204 of the server 2 constructs the value of life-and-death type, the value of gender, and the value of name for each record of the extracted record group A={a, b, c, . . . }. Data to be displayed as a child in the child area 1103 of the screen G1 sandwiched between the tags of the encrypted document is displayed in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed by a Web browser). Generate.

(Step S610)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches f, and constructs the value of the life or death type, the value of the gender, and the value of the name of the identified record. Data to be displayed on the parent area 1104 of the screen G1 sandwiched between the tags of the encrypted document is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed by a Web browser). .
In addition, the management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches m, and compares the life-and-death type value, the gender value, and the name value of the identified record. is sandwiched between tags of the structured document in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed by a Web browser). Generate.

(Step S611)
The management unit 204 of the server 2 refers to the user DB 4 and identifies a record whose personal ID value matches the personal ID value of the mother of each record in the record group R={a, b, c, . . . }. data for displaying a screen prompting the selection of candidate combinations of spouses in which the value of the life-or-death type, the value of the gender, and the value of the name of the identified record are sandwiched between tags of the structured document; 3 in a format that can be displayed on the display device 300D (for example, an HTML format that can be displayed with a Web browser).

(Step S612)
The management unit 204 of the server 2 substitutes the value of α for the local variable m.

(Step S613)
The management unit 204 of the server 2 refers to the user DB 4 and extracts a record group P={a, b, c, .

(Step S614)
The management unit 204 of the server 2 deletes duplicate records from the extracted record group P={a, b, c, . …} is extracted.

(Step S615)
The management unit 204 of the server 2 determines that the number of records in the record group R={a, b, c, . It is determined whether there are 0 persons, 1 person, or otherwise. When the number of records is "0", the management unit 204 executes the process of step S616. When the number of records is "1", the management unit 204 executes the process of step S617. If the number of records is other than "0" and "1", that is, if it is 2 or more, the management unit 204 executes the process of step S618.

(Step S616)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose individual ID value matches m, and acquires the spouse ID value f of the identified record. After that, the management unit 204 of the server 2 executes the process of step S610 in FIG. 15A.

(Step S617)
The management unit 204 of the server 2 acquires the value f of the father's personal ID in the record group R={a, b, c, . . . }. After that, the management unit 204 of the server 2 executes the process of step S608 in FIG. 15A.

(Step S618)
The management unit 204 of the server 2 refers to the user DB 4 and identifies a record whose personal ID value matches the personal ID value of the father of each record in the record group R={a, b, c, . . . }. data for displaying a screen prompting the selection of candidate combinations of spouses in which the value of the life-or-death type, the value of the gender, and the value of the name of the identified record are sandwiched between tags of the structured document; 3 in a format that can be displayed on the display device 300D (for example, an HTML format that can be displayed with a Web browser). After that, the management unit 204 of the server 2 executes the process of step S619 in FIG. 15A.

(Step S619)
The transmission unit 202 transmits (outputs) the display data generated by the management unit 204 in step S610, S611 or S618 to the user terminal 3. FIG. The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

FIG. 16 is a flow chart of the parent-child relationship viewing process 2 in the case of proceeding forward in the child direction, which is executed by the information processing system 1 according to the embodiment. In the parent-child relationship browsing process 2, if the individual arranged in the parent area 1102 of FIG. Subsequent to steps S611 to S618, it is executed after the user selects whether to display on the parent-child relationship display screen 1101 on the display screen of the user terminal 3. FIG. The value of the personal ID of the individual assigned to the father area 1104 of the parent area 1102 by selection by the user, that is, the value f of the father's personal ID for the child, and the individual of the individual assigned to the mother area 1105 of the parent area 1102 Since the ID value, that is, the mother's personal ID value m for the child, is fixed at the start of the parent-child relationship viewing process 2, the father's personal ID value is f, and the mother's personal ID value is m. I will explain as

(Step S701)
The management unit 204 of the server 2 refers to the user DB 4 and extracts a group of records A={a, b, c, . do.

(Step S702)
The management unit 204 of the server 2 constructs the value of life-and-death type, the value of gender, and the value of name for each record of the extracted record group A={a, b, c, . . . }. The display data sandwiched between the tags of the rendered document is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a Web browser).

(Step S703)
The management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches f, and constructs the value of the life or death type, the value of the gender, and the value of the name of the identified record. Data to be displayed on the parent area 1104 of the screen G1 sandwiched between the tags of the encrypted document is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed by a Web browser). .
In addition, the management unit 204 of the server 2 refers to the user DB 4, identifies a record whose personal ID value matches m, and compares the life-and-death type value, the gender value, and the name value of the identified record. is sandwiched between tags of the structured document in a format that can be displayed on the display device 300D of the user terminal 3 (for example, an HTML format that can be displayed by a Web browser). Generate.

(Step S704)
The transmission unit 202 transmits (outputs) the display data generated by the management unit 204 in steps S702 and S703 to the user terminal 3 . The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

FIG. 17 is a flowchart of a detailed display process of a family temple executed by the information processing system 1 according to the embodiment. In the following explanation, it is assumed that the user has clicked the family temple in the detailed menu 1052 of FIG. In this case, the personal ID of the individual displayed in the father area 1104 is set to individual ID: α, and the server 2 is requested to display the details of the family temple.

(Step S801)
The receiving unit 201 of the server 2 receives the request (request for detailed display of the family temple) transmitted from the user terminal 3 .

(Step S802)
The management unit 204 of the server 2 refers to the user DB 4, specifies a record whose personal ID value matches α, and acquires the parishioner ID value X of the specified record.

(Step S803)
The management unit 204 of the server 2 refers to the parishioner DB 1, specifies a record whose parity ID value matches X, and acquires the value Y of the temple of the specified record.

(Step S804)
The management unit 204 of the server 2 refers to the temple DB 2, identifies a record whose temple ID value matches Y, and displays the field values of the identified record sandwiched between structured document tags on the screen. is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a web browser).

(Step S805)
The transmission unit 202 transmits (outputs) the display data generated by the management unit 204 in step S804 to the user terminal 3 . The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

FIG. 18 is a flow chart of a grave detail display process executed by the information processing system 1 according to the embodiment. In the following explanation, it is assumed that the user has clicked the tomb in the detailed menu 1052 of FIG. In this case, the personal ID of the individual displayed in the father area 1104 is set as the individual ID: α, and the server 2 is requested to display the details of the tomb.

(Step S901)
The receiving unit 201 of the server 2 receives the request (request for detailed display of the family temple) transmitted from the user terminal 3 .

(Step S902)
The management unit 204 of the server 2 refers to the user DB 4, specifies a record whose personal ID value matches α, and acquires the parishioner ID value X of the specified record.

(Step S903)
The management unit 204 of the server 2 refers to the parishioner DB 1, specifies a record whose parity ID value matches X, and acquires the tomb ID value Y of the specified record.
(Step S904)
The management unit 204 of the server 2 refers to the tomb DB 3, identifies a record whose tomb ID value matches Y, and displays the values of each field of the identified record on the screen sandwiched between structured document tags. is generated in a format that can be displayed on the display device 300D of the user terminal 3 (for example, HTML format that can be displayed with a web browser).

(Step S905)
The transmission unit 202 transmits (outputs) the display data generated by the management unit 204 in step S904 to the user terminal 3 . The transmitted display data is received by the receiving section 301 of the user terminal 3 and displayed on the display device 300D by the display device control section 305. FIG.

As described above, the server 2 (information processing device) according to the embodiment is an information processing device that manages the final activity document data.
The server 2 includes a receiving unit 201 (receiving unit) that receives (accepts) the registration of the final activity document data, a registration unit 203 that registers the final activity document data in the database, and a management unit that manages the registered final activity document data. and a section 204 . Then, the receiving unit 201 receives designation of a user who can view the final life document data. The management unit 204 restricts viewing of the final life document data by users other than the designated user.
In this way, since access to the final life document data is restricted to users other than the specified users, the final life document data can be managed appropriately.

Further, in this embodiment, the receiving unit 201 (accepting unit) of the server 2 accepts the designation of the period when the final activity document data can be browsed, and the management unit 204 allows the browse of the final activity document data other than the specified period. limit.
In this way, in order to restrict viewing of the final activity document data other than the specified period, for example, it is possible to permit the viewing of the final activity document data during the life of the creator or after the death of the creator. Convenience improves.

Further, in this embodiment, the final life document data is divided into two or more units (chapters). Then, the receiving section 201 (receiving section) of the server 2 receives designation of a user who can view the final life document data for each unit (chapter).
In this way, since viewing is restricted for each section of the final activity document data, it is possible to allow only users intended by the creator of the final activity document to view the relevant unit (chapter) of the final activity document.

Further, in this embodiment, the receiving unit 201 (receiving unit) of the server 2 receives designation of when the final life document data can be browsed for each unit (chapter).
In this way, since viewing is restricted for each category of the final activity document data, it is possible to permit viewing of the relevant unit (chapter) of the final activity document only during the period intended by the creator of the final activity document.

Also, in this embodiment, users are classified into two or more groups, and the receiving unit 201 (receiving unit) of the server 2 receives designation of users who can browse the final life document data in group units. In addition, the management unit 204 of the server 2 restricts viewing of the final life document data by users who belong to groups other than the specified group.
In this way, since designation of users who can browse the final activity document data is accepted in group units, browsing can be permitted in group units, and convenience is improved.

Also, in this embodiment, the group includes at least one of the family temple of the creator of the final life document data and the family temple's parishioners.
In this way, it is possible to permit browsing on a group-by-group basis, such as (the priests of) the family temple or the parishioners of the family temple, thereby improving convenience.

Further, in the present embodiment, the life and death of the creator of the life and death document data and the group whose life and death can be changed are registered in the database in association with the life and death document data. Then, the receiving unit 201 (receiving unit) of the server 2 receives a change of life or death of the creator of the final life document data by the user. In addition, the management unit 204 of the server 2 changes the life or death of the creator of the final life document data when the user is classified into a group in which life or death can be changed.
In this way, it is possible to set a group that can change the life or death of the user who is the creator of the final life document. By changing the family temple in charge of the funeral of the user, the status of life/death can be changed quickly, and it is possible to prevent a priest who has no relationship with the family temple from taking charge of the funeral of the specific user.

In this embodiment, the receiving unit 201 (receiving unit) of the server 2 receives registration of at least one of information on the family temple to which the creator of the final life document data belongs and information on the cemetery where the creator is buried. The registration unit 203 of the server 2 registers at least one of the family temple information and the graveyard information in the database in association with the final life document data. Therefore, the information on the family temple and the information on the cemetery can be checked at any time.

Further, in this embodiment, the database stores the end-of-life document data and the end-of-life document data created by at least one of the parents of the creator of the end-of-life document data in association with each other. Therefore, the viewer of the end-of-life document data can trace the family lineage.

In addition, the above embodiments and modifications are merely examples of specific implementations of the present invention, and the technical scope of the present invention should not be construed in a limited manner. be. Thus, the invention may be embodied in various forms without departing from its spirit or essential characteristics.

1 information processing system 2 server (information processing device)
200A communication interface
200B storage device 200C CPU
201 receiver (reception unit)
202 transmitter (output unit)
203 registration unit 204 management unit 205 authentication unit 3 user terminal 300A communication IF
300B storage device 300C input device 300D display device 300E CPU
301 Receiving section 302 Transmitting section 303 Storage device control section 304 Operation receiving section 305 Display device control section 4 Network DB1 Family member database DB2 Temple database DB3 Tomb database DB4 User database DB5 End-of-life document database

Claims (8)

An information processing device for managing end-of-life document data,
a reception unit that receives registration of the end-of-life document data;
a registration unit that registers the final life document data in a database;
a management unit that manages the registered end-of-life document data,
The final life document data is divided into two or more units,
The reception unit
Receiving designation of a user who can view the final life document data for each of the units,
The management department
restricting viewing of the final life document data by users other than the designated user;
The database contains
information about the user's father, mother, birth order and spouse are associated and stored;
The information processing device is
An authentication unit that authenticates the user,
The management department
Information for referring to the database and presenting the blood relation when the user authenticated by the authentication unit is a child based on the information on the father, mother, birth order and spouse of the user authenticated by the authentication unit. to generate
An information processing device characterized by: The reception unit
2. The information processing apparatus according to claim 1, wherein designation of a period when the final activity document data can be browsed is accepted for each of the units. The users are classified into two or more groups including at least the parishioners of the family temple of the creator of the final life document data,
The reception unit
Receiving designation of users who can view the end-of-life document data on a per-group basis;
The management department
3. The information processing apparatus according to claim 1, wherein access to said end-of-life document data by users who are classified outside the specified group is restricted. The database contains
A creator of said final life document data and information of at least one of said creator's family member and representative user of said family member are stored in association with each other,
The management department
Referencing the database and permitting viewing of information of at least one of the parishioner and the representative user of the parishioner;
The information processing apparatus according to claim 1, characterized by: The reception unit
Receiving an instruction to retroactively or antegrade the blood relationship,
The management department
When the receiving unit receives an instruction to go back, the database is referred to, and based on the information on the father, mother, and order of birth of the user who is the starting point, the blood relationship when the user who is the starting point is a child Generate information for presenting
When the reception unit receives an instruction to proceed forward, the database is referenced, and based on the information on the children and spouses of the user who is the starting point, the blood relation when the user who is the starting point is the parent is determined. generate information for presentation,
The information processing apparatus according to claim 1 , characterized by: The management department
Determining whether there are multiple spouses of a given target person,
The reception unit
If there are multiple spouses of the predetermined target, accepting a selection of which spouse to present the blood relationship with,
6. The information processing apparatus according to claim 1 , wherein: The database contains
wherein the end-of-life document data is divided into chapters each composed of at least one or more titles and one or more texts associated with the titles and stored;
The management department
generating information for presenting the title and a portion of the text associated with the title;
7. The information processing apparatus according to any one of claims 1 to 6 , characterized in that: The database contains
a plurality of chapters included in the end-of-life document data are associated and stored;
The management department
generating information for presenting the titles of the chapters and part of the text associated with the titles in a tree-like manner based on the relevance of the plurality of chapters;
8. The information processing apparatus according to claim 7 , characterized by:

Images