JP2006185106A - Server apparatus and method for preparing personal history - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate preparing a personal history corresponding to user's interests or the like by recommending historical events which may interest the user who intends to prepare the personal history as quotation candidates. <P>SOLUTION: A personal history preparation system previously acquires information or the like concerned with preference such as user's interests, and when the user prepares his (or her) personal history, extracts and recommends historical events which may be desirable for the user on the basis of the information concerned with the preference. About historical events included in disclosed personal histories or historical events included in a common history to be used for a plurality of users in common, messages and comments such as the experiences of respective users may be registered. Further the user information of a plurality of users quoting the same historical event included in the common history for their personal histories may be mutually notified. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique for creating a personal history through a network and related techniques.

  2. Description of the Related Art Conventionally, a technique for accessing a server via the Internet and creating a personal history that can be published on the WWW (World Wide Web) is known (Patent Document 1). This conventional technique is superior in that it can display historical events in the general society alongside personal historical events.

In addition, the related art has an advantage that the user can select a history event in the general society that is registered in advance by the system administrator and that is desired to be displayed. In particular, when a user selects a desired historical event in general society, the historical event is classified into a large classification (political relation, economic relation, sports relation, etc.) and a small classification (if political relation, diplomacy, politics, international , Imperial family), and so on, so that you can select the desired historical event.
Japanese Patent Laid-Open No. 11-66049

  However, in the above-described prior art, it is necessary to search for and find a desired historical event in general society, and the user cannot immediately find a desired historical event according to his / her hobbies.

  In addition, in the above-described conventional technology, the created personal history can be disclosed on the homepage, but a third party who has seen the personal history cannot write a message on the website, and communication between users is not possible. I could n’t. In particular, there was no place to share their experiences with other historical events published in the history of others.

  Further, conventionally, even if each user creates his / her own history, a function to mediate users related to experiences and hobbies has not been provided.

  Therefore, an object of the present invention is to solve at least one of such problems and other problems. Other issues can be understood throughout the specification.

  According to the first aspect of the present invention, when information about preferences such as a user's hobby is acquired in advance and the user creates his / her own history, it is preferable for the user based on the information about the preferences. Extract and recommend possible historical events.

  According to the second aspect of the present invention, messages, comments, etc., such as experiences of each user, regarding a historical event included in a public history or a historical event included in a common history shared by a plurality of users. Register.

  According to the third aspect of the present invention, user information can be notified to a plurality of users who have cited the same historical event included in the common history in their own history.

  According to the first aspect of the present invention, since a history event that may be of interest to a user who wants to create his / her own history is recommended as a citation candidate, the user can select his / her own history according to his / her hobbies and the like. Makes it easier to create.

  According to the second aspect of the present invention, the user can comment and announce his / her own experiences and the like for each historical event. Eventually, it will be possible to easily collect historical experiences at the level of the general public, which has required a lot of trouble with conventional collection.

  According to the 3rd viewpoint of this invention, it becomes easy to mediate common users, such as a hobby and experience. Eventually, it will be possible to support communication between these users.

  In the following, an embodiment useful for understanding the high-level concept, middle-level concept, and low-level concept of the present invention will be described. Note that not all of the concepts included in the following embodiments are described in the claims. However, it should be understood that this is not intentionally excluded from the technical scope of the patented invention, but is not described in the scope of claims because it is equivalent to the patented invention.

  In the following, the technical idea as a superordinate concept will be described first with reference to the drawings, and then several examples corresponding to the intermediate concept or the subordinate concept will be introduced.

  According to a first aspect of the present embodiment, a server device that creates a user's own history that can be disclosed on a network, the first database storing preference profiles related to each user's preferences, A second database that stores a description of each historical event that occurred in the database, identification information for identifying each historical event, and attribute information that represents an attribute of the historical event, and a user who wants to create his own history The preference profile reading means for reading the preference profile from the first database, the attribute information matching the read preference profile is extracted, and the history event associated with the extracted attribute information And a history event reading means for reading out the history from the second database; Server apparatus is provided, characterized in that the recommendation information for recommending the event description by reference candidate to personal history of the user and a recommendation information sending means for sending to the terminal device of the user.

  According to the first aspect, since a history event that may be of interest to a user who wants to create his / her own history is recommended as a citation candidate, the user can create his / her own history according to his / her hobbies. It becomes easy to do.

  According to a second aspect, the source file creation means for creating a source file describing the user's own history and the browsing request for the user's own history from another user's terminal device, You may include the source file transmission means which transmits a source file in the server apparatus of the 1st viewpoint.

  According to this viewpoint, the user's own history can be easily disclosed on the Internet by creating the user's own history in a source file format such as an HTML file. In addition, there is an advantage that it is easy to operate a website providing a personal history creation service on the Internet.

  According to a third aspect, the quotation request receiving means for receiving a quotation request for quoting the user's own history about the explanation of the history event recommended by the recommendation information from the user's terminal device; A third database that stores the identification information of the historical event that is the target of the citation request in association with the identification information of the user, and the source file creation means includes the identification information of the user that is the creation target of the own history Based on the above, the identification information of the historical event that is the target of the citation request is read from the third database, and the description of the historical event associated with the read identification information of the historical event is read from the second database. It is characterized in that the history event read out is described in the source file of the personal history. It may constitute a server device of the second aspect to.

  According to this aspect, the user can select an arbitrary historical event from the recommended information of general historical events with a pointing device or the like, and can quote it in his / her own history. Is much easier than before.

  According to a fourth aspect, for the explanation of the historical event stored in the second database, a memorandum data receiving means for receiving memorandum data transmitted from the user terminal, and the received memorandum The server device according to the third aspect is further configured to further include means for writing the identification information of the user who is the sender of the data and the memorandum data in the third database in association with the identification information of the historical event. May be.

  According to this aspect, when quoting a specific general historical event in his / her own history, a memorandum about the historical event can be held in the database. If the user refers to the memorandum later, it will be easier to remember the experience for the historical event. Also, by extracting each user's memorandum about a specific historical event, it will be possible to easily collect historical experiences at the level of the general public, which previously required a lot of effort.

  According to the fifth aspect, when the description of the specific historical event is described in the source file of the personal history, the identification information of the other users who quote the description of the historical event is used as the third database. The server apparatus according to the third aspect is configured to further include a user identification information search unit that searches and extracts from the source file, and the source file creation unit describes the identification information of the other users that are searched and extracted in the source file. May be.

  According to this viewpoint, it becomes easy to mediate users who share a hobby or experience. Eventually, it will be possible to support communication between these users.

  According to a sixth aspect, the first bulletin board described above further includes an electronic bulletin board execution means for writing a message such as an opinion about the experience story or information written by other users about the specific historical event. You may comprise the server apparatus in any one of a viewpoint thru | or a 5th viewpoint.

  According to this viewpoint, the user can comment and announce his / her own experiences and the like for each historical event. Eventually, it will be possible to easily collect historical experiences at the level of the general public, which has required a lot of trouble with conventional collection. In addition, by adopting a technique called an electronic bulletin board, it is possible to provide a place where users can talk to specific historical events and others about comments. This makes it easier for the user to awaken the forgotten experience. This will make it easier to collect historical experiences at the general public level.

  According to a seventh aspect, the apparatus further includes a fourth database storing a description of a user's personal history event, wherein the source file creation means includes the personal history event of the user for which the history is created. The server device according to any one of the first to sixth aspects may be configured so that the description is described in the source file.

  From this point of view, not only general historical events but also personal historical events can be announced as personal history. This allows other users to enjoy viewing personal history events. In addition, other users will easily find a user having an experience similar to that of the user.

  According to an eighth aspect, the method further comprises comment writing means for writing a comment from another user to the user's personal history event description in the fourth database, wherein the source file creating means includes When creating the source file of the user's own history, the comment for the specific personal history event is read from the fourth database, and the read comment is described in the source file. You may comprise the server apparatus of a viewpoint.

  Other users can write comments on other users' personal historical events, making it easier for other users to write their experiences and opinions about the personal historical events. Let's go.

  In the following, an example of the invention corresponding to the middle concept and the lower concept for the above-described superordinate concept will be described.

  FIG. 1 is a diagram illustrating an example of a self-history system according to the embodiment. The server device 100 is a computer on which various control programs according to the present invention are installed, and is a main part for realizing creation of one's own history, display of one's own history, display of the history of all, and the like. Everyone's history (shared history) is chronological data that registers general historical events. The database 101 is a storage device that stores member data, personal history data, and personal history data. A member is a user who is permitted to use the service by the personal history system. The personal history service network 105 is a communication network such as a LAN, a WAN, and the Internet. The PCs 110a to 110z are computers (terminal devices) of each member. In addition, when demonstrating a process common to PC110a-z, suffix az is abbreviate | omitted and it describes as PC110.

  FIG. 2 is a diagram illustrating an example of various databases according to the embodiment. The member management database 201 is a database for managing information related to members of the personal history system. The member management database 201 includes member identification information (ID) for identifying each member, authentication password information, nickname information, date of birth information, gender information, and residence information. Information and preference profile information. The preference profile is information for specifying each member's hobbies, interested information, and the like.

  The everyone history database 202 is a database for registering general history events. A general historical event (hereinafter referred to as a topic) is a historical event that is distinct from each member's personal experience event (hereinafter referred to as a section). For example, “August 15, 1945 end of war” is a common historical event. On the other hand, for example, “XX Elementary School Admission” is a personal experience event.

  The personal history database 202 includes topic identification information (ID) for identifying each topic, and information such as a topic occurrence date, a topic title, a topic text, and an item. The title of the topic is a kind of explanation and is information that briefly represents the content of the topic, such as “End of War”. The text of the topic is a kind of explanation, for example, “The Government of Japan has accepted the Potsdam Declaration and the Pacific War has ended.” The item is closely related to each attribute included in the above-described preference profile, and is information that becomes a key when searching and extracting a history topic according to each member's preference.

  The everyone history bulletin board database 203 is a database that stores messages of members for each history topic. This message is a message of a member written on a bulletin board on the web provided for each history topic. Each message includes personal experiences about specific historical topics and opinions and comments about others' messages. As a result, it is possible to efficiently collect historical experiences at the level of general people who have been difficult to collect.

  In the everyone history bulletin board database 203, information such as topic ID, identification information (ID) of the message written on the bulletin board for each topic, member ID of the member who wrote the message, message text, message registration date, and the like. include.

  The personal history section database 204 is a database for storing history sections registered in the personal history of each member. The personal history section database 204 includes identification information (section ID) for identifying each section, information such as the occurrence date of the section, member ID, section title, section text, and comments from other members. It is. In addition to comments on the section, comments from other members may include member IDs of the other members, information on the date of comment registration, and the like. In the present invention, personal comments of others can be accumulated in a section of an arbitrary member, so that members who may be interested in a specific section can be brokered.

  The personal history topic database 205 is a database for managing historical topics cited in the personal history of each member. The personal history topic database 205 stores a member ID of each member, a historical topic ID cited by the member in his / her own history, a memorandum for the historical topic, and the like.

  The item database 206 is used for investigating the relevance between topics and searching for topics according to a member's preference profile. The item database 206 stores items and attribute information corresponding to the items. An item is information such as a noun that can be used as a keyword, and is usually information closely related to the title or text of a topic. For example, if the topic is “Manga artist A announces Manga B.”, the items are “Manga artist A” and “Manga B”. The attribute information is information for classifying items. If the item is “cartooner A”, the attribute information is “cartooner”.

  FIG. 3 is an exemplary functional block diagram of the server apparatus according to the embodiment. Hereinafter, typical functions of the server device will be described. The web server unit 301 is a unit for transmitting web page data such as an html file and image data to the user PC 110. It is also a unit realized when a control unit such as a CPU executes a web server program such as httpd.

  The web page creation unit 302 is a unit for creating various page data (such as a source file) related to the user's history. Other units may include a more individual page data creation function. The web page creation unit 302 stores several template files in a storage device such as a hard disk, reads the template file, and appropriately arranges the data read from the tags and the database in the template file. , Page data (source file etc.) may be created.

  For example, when displaying or creating the member's own history, the unit 302 recommends information such as a topic title read by the topic search unit 305 as a candidate for citation to the member's own history (for example, recommended A source file for displaying a topic list or the like may also be created.

  Further, when the unit 302 reflects the information of the citation topic in its own history, the web page creation unit 302 selects the topic that is the target of the citation request based on the identification information of the member that is the subject of its history. The identification information is read from the personal history topic database 205, and the topic search unit 305 is searched for the topic title and text associated with the read topic identification information. Then, the extracted topic information may be described in the source file of one's own history.

  Further, the unit 302 uses the topic search unit 305 to describe the identification information of other members who cite the topic from the personal history topic database 205 when describing a specific topic in the personal history source file. It is also possible to search and extract and describe the identification information of other users that have been searched and extracted in the source file.

  When the unit 302 receives a comment from another member about the member's personal history event (section), the unit 302 writes it in the own history section database 204. Also, when creating a source file of a member's own history, a comment on a topic cited in the member's own history is read from the own history section database 204, and the read comment is described in the source file.

  The member registration unit 303 receives a new member registration request transmitted from the PC 110 of the user who is a member, and manages a member ID for identifying the member and a preference profile representing an interest of the member. This is a unit for registering in the database 201.

  The personal history creation unit 304 is a unit for creating personal history data of each member. The personal history creation unit 304 writes information such as the section occurrence date, title, and text transmitted from the member's PC 110 into the personal history section database 204. A section is a user's personal historical event.

  Further, when the unit 304 receives from the PC 110 a citation request for quoting a topic recommended by the recommended information in its own history, the unit 304 associates the identification information of the topic that is the target of the citation request with the identification information of the member. Write to the history topic database 205. When the personal history creation unit 304 receives the memorandum data transmitted from the PC 110 for the topic stored in the history database 202, the personal history creation unit 304 uses the received memorandum data and the identification information of the member who is the sender as the topic. Is written in the personal history topic database 205 in association with the identification information.

  The topic search unit 305 is a unit that searches and extracts related topics from the history database 202 in response to a search request transmitted from the PC 110 or a search request from any other unit. For example, this unit reads a preference profile related to a user who wants to create his / her own history from the member management database 201, extracts attribute information that matches the read preference profile from the item database 206, and extracts the extracted attribute information. All of the related topic titles and texts are read from the history database 202.

  A bulletin board management unit 306 for a topic is a unit for managing an electronic bulletin board displayed when a specific topic is selected. The bulletin board management unit 306 for a topic writes all messages such as opinions about an own story about a specific topic or information written by other members in the history bulletin board database 203. Also. The member ID, message text, and registration date information stored in association with the ID of the selected topic are all read from the history bulletin board database 203. Further, in response to a message write request received from the PC 110, a message ID is assigned to the message for the topic, and the member ID, message text, and registration date information are all written in the history bulletin board database 203.

  The personal history search unit 307 is a unit that searches and extracts related personal history sections from the personal history section database 204 based on a member's nickname, date of birth, section keyword, and the like.

  The comment addition unit 308 for the section is a unit that controls a comment addition process for the section of the personal history searched and extracted by the personal history search unit 307. For example, the comment adding unit 308 writes the input comment in the personal history section database 204 in association with the ID of the selected section.

  FIG. 4 is an exemplary hardware block diagram of the server device according to the embodiment. The control unit 401 is a processing circuit such as a CPU that comprehensively controls each function of the server device 100. The storage unit 402 is a storage device such as a ROM, a RAM, and a hard disk drive, and stores a control program 410 and various databases 201 to 206. The control program includes a computer program for realizing the various functional units shown in FIG. The transmission / reception unit 403 is a communication device such as a communication card, and is connected to the network 105.

  FIG. 5 is an exemplary hardware block diagram of the user PC according to the embodiment. The control unit 501 is a processing circuit such as a CPU that comprehensively controls each function of the PC 110. The storage unit 502 is a storage device such as a ROM, a RAM, and a hard disk drive, and stores a control program 510 and the like. The control program includes an execution environment program for executing a web browser program and a Java (registered trademark) applet. The transmission / reception unit 503 is a communication device such as a network communication card, and is connected to the network 105. The input unit 504 is an input device such as a keyboard and a pointing device. The display unit 505 includes a display control circuit, a display device, and the like.

  FIG. 6 is a flowchart of the main routine of the personal history system according to the embodiment. When all the systems are configured with web technology, the end point of the main routine is not necessarily clear, but for convenience, “END” is described in the flowchart.

  When the control unit 401 of the server apparatus 100 receives an HTML source file transmission request from the PC 110 to the main page via the transmission / reception unit 403, the control unit 401 reads the HTML source file of the main page from the storage unit 402 and transmits it to the PC 110. The control unit 501 of the PC 110 analyzes the HTML source file received through the transmission / reception unit 503 using a browser program, creates display data for the main page, and displays it from the display unit 505. When it is necessary to download image data or the like, the PC 110 receives necessary image data from the server device 100 and reflects it in the display data of the main page.

  FIG. 7 is a diagram illustrating an example of a main page of the personal history site according to the embodiment. On this main page, links to other pages are set. As links, for example, a link 701 to a new member registration page for enjoying the service of the personal history site, a link 702 to a personal history creation page for creating personal history, and a search for topics of history for everyone. A link 703 to the topic search page, a link 704 to the personal history search page for searching the personal history of others, and the like are included. Each link can be clicked by a pointer 705 that is linked to the operation of the pointing device of the input unit 504.

When a click on any link is input from the input unit 504 of the PC 110, a transmission request for a page associated with the link is transmitted to the server apparatus 100. The server device 100 reads the page source file in accordance with the URL included in the received transmission request, and transmits it to the PC 110. For example, when a new member registration page is requested, the control unit 401 of the server apparatus 100 proceeds to step S602 and executes a new member registration process. If the request is for a self-history creation page, the control unit 401 proceeds to step S603 and starts a self-history creation process. If the request is for a topic search page, the control unit 401 proceeds to step S604 and starts topic search processing. If it is a request for the personal history search page, the control unit 401 proceeds to step S605 and starts the personal history search process.
<New member registration process>
FIG. 8 is an exemplary flowchart of a new member registration process according to the embodiment. This process corresponds to the subroutine of step S602 executed mainly by the member registration unit 303. In the following description, it is assumed that the member registration unit 304 is realized by the control unit 401 and the control program 410 of the server device 100.

  In step S <b> 801, the control unit 401 reads the source file of the new member registration page from the storage unit 402, and transmits the source file to the PC 110 through the transmission / reception unit 403. The control unit 501 of the PC 110 renders the received source file and causes the display unit 505 to display a new member registration page.

  FIG. 9 is a diagram illustrating an example of a new member registration page according to the embodiment. The page includes a text box and a radio button for inputting information related to the member ID, nickname, password, date of birth, and sex. When a member ID or the like is input from the input unit 504 and the transmission button 901 is clicked, the input information is transmitted to the server device 100.

  In step S <b> 802, when the control unit 401 of the server apparatus 100 receives the input information, the control unit 401 registers the received information in the member management database 201.

  In step S <b> 803, the control unit 401 reads the source file of the preference profile selection page from the storage unit 402 and transmits it to the PC 110. When receiving the source file of the preference profile selection page, the control unit 501 of the PC 110 displays the page on the display unit 505.

  FIG. 10 is a diagram illustrating an example of a preference profile selection page according to the embodiment. In this example, major classifications such as serious news, life, culture and sports are shown. In addition, under major news, subcategories such as politics / economy, society, science, disaster, international, and others are shown with check boxes.

  In step S804, the control unit 501 of the PC 110 transmits information on an arbitrary check box checked by the input unit 505 (such as a pointing device) (referred to as preference attribute information) to the server apparatus 100. The control unit 401 of the server apparatus 100 receives preference attribute information from the PC 110.

  In step S805, the control unit 401 writes the received preference attribute information as a preference profile in the member management database 201. At this time, it may be controlled so that the preference profile information is written in the member management database 201 together with the member ID and password.

In this way, the ID of the new member can be registered in the member management database 201. This also allows new members to enjoy personal history creation services on their personal history sites.
<Login member's personal history display and personal history creation process>
FIG. 11 is an exemplary flowchart of a login member's own history display and own history creation process according to the embodiment. This process corresponds to the subroutine of step S603 executed by the above-mentioned own history creation unit 304. In the following description, it is assumed that the member registration unit 304 is realized by the control unit 401 and the control program 410 of the server device 100.

  In step S1101, the control unit 401 executes a member authentication process. For example, the control unit 501 transmits a login page as shown in FIG. 7 to the PC 110, receives the user ID and password transmitted from the PC 110, and registers the received user ID and password in the member management database 201. It is judged whether it is done. Thereby, member authentication is executed.

  In step S1102, the control unit 401 creates a personal history page related to the logged-in member.

  FIG. 12 is an exemplary flowchart of the personal history creation process according to the embodiment.

  In step S1201, the control unit 401 searches the personal history section database 204 using the member ID as a search condition, and extracts information such as the occurrence date, title, text, and comment of the section related to the member ID. The control unit 401 sorts the extracted sections for each occurrence date, and creates member chronological data.

  Further, the control unit 401 searches the personal history topic database 205 using the member ID as a search condition, and extracts the cited topic ID. Further, using the extracted cited topic ID as a search condition, everyone searches the history database 202 to extract the occurrence date, title, text, and item of the related topic. The control unit 401 sorts the extracted topics for each occurrence date, and creates chronological data related to general history topics.

  In step S1202, the control unit 401 searches the member management database 201 using the member ID as a search condition, and extracts a preference profile related to the member ID. Further, using the attribute information included in the extracted preference profile as a search condition, the item database 206 is searched to extract item data related to the attribute information. Further, the control unit 401 searches the history database 202 using the extracted item data as a search condition, and extracts the topic ID, title, and the like of related topics. The control unit 401 creates a list of topics recommended for the member from the extracted topic ID, title, date of occurrence, and the like.

  In step S1203, the control unit 401 creates a source file of the personal history page including the created chronological data of the individual members, chronological data regarding general historical topics, and a title list of recommended topics.

  In addition, on the personal history page, tags related to the section addition button for adding a new section to the member's individual chronological data and the topic addition (search) button for adding a topic to the chronological data on general history topics May be described.

  Each topic title included in the recommended topic title list may be described as a link to a topic page. The topic page may include a body text relating to the topic title, a topic addition button for adding the topic to chronological data relating to a general history topic, or the like of a member.

  In step S1103, the control unit 401 transmits the created source file of the personal history page (image data when requested by the PC 110) to the PC 110. When the control unit 501 of the PC 110 receives the source file, the control unit 501 creates display data by a web browser program and displays the personal history page on the display unit 505.

  FIG. 13 is a diagram illustrating an example of a personal history page according to the embodiment. In the personal history page of this example, a member's personal chronological data 1301, a chronological data 1302 regarding general historical topics, a recommended topic title list 1330, and a member's personal chronological data 1301 for adding a new section. A section addition button 1311 and a topic addition (search) button 1312 for adding a topic to chronological data relating to a general history topic are included. The personal history page may be created every predetermined period such as every 10 years. In this case, each personal history page can be switched by the age designation link 1320.

  In the member's individual chronological table data 1301, a section generation year 1303, a section generation date 1304, and a section title 1305 are displayed. The section occurrence date 1304 and the section title 1305 include a link to a page displaying the section text.

  The chronological data relating to general history topics includes a topic title 1306 and a link 1307 to a page displaying the topic text. Also included is a link 1310 to a page displaying a memorandum for the topic. Here, as for the topic to be displayed, the one generated at the same time as the section to be displayed at the same time is retrieved and extracted. That is, the section occurrence time is set as a topic search condition.

  The recommended topic title list 1303 includes a topic title 1308 and information 1309 of the topic occurrence year. The topic title 1308 has a link to a page that displays the topic text. Here, as for the recommended topic to be displayed, those that occur at the same time as the section to be displayed at the same time are retrieved and extracted. That is, the section occurrence time is set as a topic search condition.

  When the section addition button 1311 is included in the personal history page and the button is clicked by the input unit 504, the control unit 501 sends a section addition request (such as a transmission request for a section addition page) to the server apparatus 100. Send.

  In step S <b> 1104, the control unit 401 of the server apparatus 100 determines whether a section addition request has been received through the transmission / reception unit 403. If the section addition request is received, the process proceeds to step S1105, and the control unit 401 transmits the source file of the section addition page. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a section addition page on the display unit 505.

  FIG. 14 is a diagram illustrating an example of a section addition page according to the embodiment. The page includes a text box 1401 and a radio button 1402 for inputting a section generation date, a text box 1403 for inputting a section title, a text box 1404 for inputting a section body, and input information. A button 1405 for transmitting to the server apparatus 100 is included. The control unit 501 transmits the information input here as additional section information to the server device 100.

  In step S1105, when the control unit 401 receives additional section information from the PC 110, the control unit 401 registers the additional section information in the own history section database 204 in step S1106. The section ID is assigned a serial number by the control unit 401. The member ID is the member ID of the currently logged-in member. Comments from other members are left blank.

You can display your history and add sections to your history. As for adding a topic to one's own history, an arbitrary topic can be searched and added, or one of recommended topics can be selected and added. These processes will be described later.
<Topic search>
FIG. 15 is an exemplary flowchart of a topic search process according to the embodiment. This process corresponds to the topic search / display process of step S604 executed by the control unit 401. Thereby, the topic search unit 305 and the bulletin board management unit 306 are realized.

  In step S <b> 1501, the control unit 401 of the server apparatus 100 reads a source file of an input page for inputting a keyword or the like for searching for a specific topic from the history database 202 from the storage unit 402 and transmits it to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a keyword input page on the display unit 505.

  FIG. 16 is a diagram illustrating an example of a keyword input page according to the embodiment. The page of this example includes a text box 1601 for designating a topic generation year, a text box 1602 for inputting a free keyword, and a radio button group 1603 for designating predefined topic attributes. Yes. When the search button 1604 is pressed after these keywords are input, the control unit 501 transmits a search request including the keywords to the server device 100.

  In step S <b> 1502, the control unit 401 of the server apparatus 100 receives a search request by the transmission / reception unit 402.

  In step S1503, the control unit 401 searches and extracts related topics from the history database 202 using the keywords included in the received search request as search conditions.

  In step S <b> 1504, the control unit 401 creates a search result page source file including search results (topic generation date, topic title, item, etc.), and transmits it to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a search result page on the display unit 505.

  FIG. 17 is a diagram illustrating an example of a search result page according to the embodiment. The page includes a topic occurrence date 1701, an item 1702, and a topic title 1703. The topic title 1703 has a link to a page that displays detailed information such as the topic text. Although it is a technical matter well known to those skilled in the art, “linked” means that a link tag for designating a specific URL is included in the source file.

  In step S <b> 1505, when any topic title 1703 is selected by a click operation on the input unit 504, the control unit 501 transmits a pick selection request (such as a link destination page transmission request) to the server apparatus 100. The control unit 401 of the server apparatus 100 receives the topic selection request via the transmission / reception unit 403.

  In step S <b> 1506, the control unit 401 creates a source file for the selected topic page, and transmits it to the PC 110.

  FIG. 18 is an exemplary flowchart regarding a topic display process according to the embodiment. The flowchart is a subroutine of step S1506, and is executed by the control unit 401. This is also a function of the web page creation unit 302, the bulletin board management unit 306, and the topic search unit 305.

  In step S <b> 1801, the control unit 401 reads the topic text and the like for the selected topic from the history database 202.

  In step S1802, the control unit 401 extracts data (message ID, member ID, message text, message registration date, etc.) necessary for creating a bulletin board from the bulletin board database 203 using the ID of the selected topic as a search condition. To do. Further, the control unit 401 reads a nickname from the member management database 201 using the member ID as a search condition.

  In step S1803, the control unit 401 creates a topic display page including the read topic occurrence date, topic title, topic body, and the like. When displaying the bulletin board at the same time, the message registration date, the nickname of the message writer, and the message body are also described in the source file of the topic display page.

  In step S1804, the control unit 401 transmits the created source file of the topic display page to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a topic display page on the display unit 505.

  FIG. 19 is a diagram illustrating an example of a topic display page according to the embodiment. The page includes a topic display unit 1900, a bulletin board display unit 1910, and a message writing unit 1920 for the bulletin board. A list 1930 of related topics and a list 1940 of members who cite the topic being displayed in their own history may be included.

  The topic display unit 1900 includes a topic occurrence date 1901, a topic title 1902, and a topic text 1903. When it is desired to add the topic to the user's own history, when the add topic button 1904 is pressed, the control unit 501 of the PC 110 transmits a topic addition command to the server apparatus 100.

  The bulletin board display unit 1910 includes a message registration date 1911, a nickname 1912 of a message writer, and a message body 1913.

  The message writing unit 1920 for the bulletin board includes a text box 1921 for inputting a new message and a writing execution button 1922. When the control unit 501 of the PC 110 detects that the write execution button 1922 has been operated by the input unit 504, the control unit 501 transmits a message addition command that is input and includes a message to the server apparatus 100.

  The related topic list 1930 is created as follows. The control unit 401 reads all items of the topic currently being displayed from the history database 202. Next, using the item as a search condition, the everyone history database 202 is searched to extract a topic ID, a topic occurrence date, a topic title, and the like. The control unit 401 creates related topic list data 1930 including the extracted topic occurrence date and topic title, and describes them in the source file of the topic display page. Note that the topic title of the related topic list data 1930 may be a link to a page displaying the topic.

  Thus, by displaying the related topics as a list, the member can easily display other topics related to the current topic. In addition, it becomes easy to access the bulletin board of the related topic, and it becomes easy to quote the related topic in one's own history.

  A list 1940 of members citing the same topic is created as follows. First, the control unit 401 searches the personal history topic database 205 using the topic ID of the topic being displayed as a search condition, and extracts a member ID and memorandum data. Further, the nickname is extracted from the member management database 201 using the member ID as a search condition. The control unit 401 creates member list data 1940 including the extracted nickname and memorandum data, and describes it in the source file of the topic display page. The nickname portion may be a link to the history of the member of the nickname.

  In this way, the member list data 1940 can mediate other members who cite the same topic.

  In step S1805, the control unit 401 determines whether a message addition command has been received. If a message addition command has been received, the process advances to step S1806, and the control unit 401 generates a new message ID. Further, the control unit 401 registers the ID of the topic to be added, the generated message ID, the ID of the member who has transmitted the message addition command, the received new message (text), and the message obtained from the timer. A new entry including the date is created and registered in the bulletin board database 203. As a result, the bulletin board database 203 is updated.

  Thereafter, the process returns to step S1507, and the control unit 401 determines whether or not a request for adding to the own history has been received for the selected topic. If received, the process proceeds to step S1508, and the control unit 401 creates a source file for displaying the input page of the memorandum data and transmits it to the PC 110.

  FIG. 20 is a diagram illustrating an example of the memorandum data input page according to the embodiment. The topic display unit 2000 is the same as the topic display unit 1900 of FIG. The memorandum data input unit 2010 includes a text box 2011 for inputting memorandum data and an execution button 2012 for transmitting the inputted memorandum data to the server apparatus 100. When the operation of the execution button 2012 is detected, the control unit 501 transmits a registration request including the memorandum data input in the text box 2011 to the server apparatus 100.

  In step S <b> 1509, the control unit 401 of the server apparatus 100 receives a memorandum data registration request through the transmission / reception unit 403.

  In step S1510, the control unit 401 reads the memorandum data from the received memorandum data registration request. Further, the control unit 401 creates a new entry including the member ID, the ID of the topic to be added, and memorandum data, and writes the new entry in the personal history topic database 205.

As described above, an arbitrary topic can be displayed. In addition, a bulletin board is provided for discussing one's own experiences about the displayed topic. In addition, you can select any of the displayed topics and quote it in your history. Also, when adding a topic to your history, you can register your experiences and other information in the database as memorandum data.
<Search process of your history>
In the following, a process for searching another person's own history will be described. Searching other people's own history will make it easier to find people with similar circumstances.

  FIG. 21 is an exemplary flowchart of a personal history search process according to the embodiment. The functions realized by this flowchart are a personal history search unit 307, a comment addition unit 308, and the like.

  In step S <b> 2101, the control unit 401 reads the keyword input page source file from the storage unit 402 and transmits it to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a keyword input page on the display unit 505.

  FIG. 22 is a diagram illustrating an example of a keyword input page according to the embodiment. The page includes a text box 2201 for designating the age of the member, a radio button 2202 for designating the gender of the member, a list box 2203 for designating the residence of the member, and a text for inputting a free keyword. A box 2204 and an effective button 2205 for sending a search request are included. When the control unit 501 of the PC 110 detects that the execution button 2205 is operated by the input unit 504, the control unit 501 transmits a search request including the input keyword to the server apparatus 100.

  In step S2102, the control unit 401 of the server apparatus 100 receives a search request including a keyword.

  In step S2103, the control unit 401 searches the personal history section database 204 or the like using the received keyword (for example, age, gender, residence, free keyword, etc.) as a search condition. For example, the control unit 401 searches the member management database 201 using the received age, sex, and residence as search conditions, and extracts the corresponding member ID. Subsequently, the personal history section database 204 is searched using the extracted member ID and the received free keyword as a search condition, and related sections are extracted. Note that the nickname of the member is also read from the member management database 201 based on the extracted member ID.

  In step S <b> 2104, the control unit 401 creates a page source file for displaying the search result, and transmits it to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a search result display page on the display unit 505.

  FIG. 23 is a diagram illustrating an example of a search result display page according to the embodiment. The page includes the extracted member nickname 2301, member age 2302, gender 2303, and residence 2304. Further, the page includes a section title 2305 and a section text 2306. The section title 2305 has a link to a page for displaying the section text in detail or writing a comment. When the control unit 501 of the PC 110 detects that the link is clicked by the input unit 504, the control unit 501 transmits a section display request (such as a transmission request for a link destination page) to the server apparatus 100.

  In step S <b> 2105, the control unit 401 receives a section display request via the transmission / reception unit 403.

  In step S2106, the control unit 401 searches and extracts the section occurrence date, the section title, the section text, and comments from other members from the section database 204 for the section requested to be transmitted by the section display request. Create a source file and send it to the PC 110. When receiving the source file, the control unit 501 of the PC 110 creates display data by a web browser program and displays a section detail page on the display unit 505.

  FIG. 24 is a diagram illustrating an example of a section detail page according to the embodiment. The section display section includes a section occurrence date 2401, a section title 2402, and a section body 2403. In addition, comments 2405 from other members for the section are also included. Further, a text box 2406 for writing a new comment and an execution button 2407 for executing writing of a comment are also included. When detecting an operation from the input unit 504 with respect to the write button 2407, the control unit 501 transmits a comment write request including comment data input to the text box 2406 to the server apparatus 100.

  In step S2107, the control unit 501 determines whether a comment write request has been received. If received, the process proceeds to step S2108, and the control unit 501 writes the comment received together with the comment writing request with the corresponding section ID and writes it in the own history section database 204.

FIG. 1 is a diagram illustrating an example of a self-history system according to the embodiment. FIG. 2 is a diagram illustrating an example of various databases according to the embodiment. FIG. 3 is an exemplary functional block diagram of the server apparatus according to the embodiment. FIG. 4 is an exemplary hardware block diagram of the server device according to the embodiment. FIG. 5 is an exemplary hardware block diagram of the user PC according to the embodiment. FIG. 6 is a flowchart of the main routine of the personal history system according to the embodiment. FIG. 7 is a diagram illustrating an example of a main page of the personal history site according to the embodiment. FIG. 8 is an exemplary flowchart of a new member registration process according to the embodiment. FIG. 9 is a diagram illustrating an example of a new member registration page according to the embodiment. FIG. 10 is a diagram illustrating an example of a preference profile selection page according to the embodiment. FIG. 11 is an exemplary flowchart of a login member's own history display and own history creation process according to the embodiment. FIG. 12 is an exemplary flowchart of the personal history creation process according to the embodiment. FIG. 13 is a diagram illustrating an example of a personal history page according to the embodiment. FIG. 14 is a diagram illustrating an example of a section addition page according to the embodiment. FIG. 15 is an exemplary flowchart of a topic search process according to the embodiment. FIG. 16 is a diagram illustrating an example of a keyword input page according to the embodiment. FIG. 17 is a diagram illustrating an example of a search result page according to the embodiment. FIG. 18 is an exemplary flowchart regarding a topic display process according to the embodiment. FIG. 19 is a diagram illustrating an example of a topic display page according to the embodiment. FIG. 20 is a diagram illustrating an example of the memorandum data input page according to the embodiment. FIG. 21 is an exemplary flowchart of a personal history search process according to the embodiment. FIG. 22 is a diagram illustrating an example of a keyword input page according to the embodiment. FIG. 23 is a diagram illustrating an example of a search result display page according to the embodiment. FIG. 24 is a diagram illustrating an example of a section detail page according to the embodiment.

Claims (9)

A server device that creates a user's own history that can be disclosed on the network,
A first database storing preference profiles for each user preference;
A second database that stores a description of each historical event that has occurred in history, identification information for identifying each historical event, and attribute information representing an attribute of the historical event in association with each other;
Preference profile reading means for reading from the first database the preference profile related to a user who wishes to create his own history;
History event reading means for extracting the attribute information that matches the read preference profile and reading a description of the history event associated with the extracted attribute information from the second database;
A server apparatus comprising: recommended information transmitting means for transmitting recommended information for recommending the read explanation of the history event as a candidate for citation to the user's own history to the terminal device of the user. Source file creation means for creating a source file describing the user's own history;
The server apparatus according to claim 1, further comprising source file transmission means for transmitting the created source file when receiving a request for browsing the own history from a terminal device of another user. A quote request receiving means for receiving a quote request for quoting the user's own history about the explanation of the history event recommended by the recommendation information from the terminal device of the user;
A third database that stores the identification information of the historical event that is the target of the citation request in association with the identification information of the user;
The source file creation means reads out the identification information of the historical event that is the target of the citation request from the third database based on the identification information of the user that is the target of creation of its own history, and 3. The server according to claim 2, wherein a description of the historical event associated with identification information is read from the second database, and the read description of the historical event is described in the source file of the personal history. apparatus. Memorandum data receiving means for receiving memorandum data transmitted from the terminal of the user in response to the description of the historical event stored in the second database;
Means for writing the received memorandum data and the identification information of the user who is the sender of the memorandum data to the third database in association with the identification information of the historical event;
The server device according to claim 3, further comprising: User identification information search that searches and extracts identification information of other users who are citing the history event description from the third database when describing the description of the specific history event in the source file of the own history Further comprising means,
4. The server apparatus according to claim 3, wherein the source file creating means describes the identification information of the other user retrieved and extracted in the source file.   6. The server apparatus according to claim 1, further comprising an electronic bulletin board execution unit for writing a message such as an opinion about the specific historical event or an opinion on information written by another user. A fourth database that stores descriptions of the user's personal historical events;
The server device according to claim 1, wherein the source file creation unit describes the explanation of the personal history event related to a user who is a creation target of own history in the source file. Comment writing means for writing comments from other users to the user's personal historical event descriptions in the fourth database;
When creating the source file of the user's own history, the source file creation means reads the comment for the specific personal history event from the fourth database, and reads the read comment into the source file. The server device according to claim 7, wherein the server device is described. A self-history creation method for creating a self-history of a user that can be disclosed on a network in a server device,
Reading from the first database the preference profile relating to users who wish to create their own history from a first database storing preference profiles relating to the preferences of each user;
The preference profile read from the second database that stores the description of each historical event that occurred in history, identification information for identifying each historical event, and attribute information that represents the attribute of the historical event in association with each other Extracting the attribute information that is consistent with and reading the description of the historical event associated with the extracted attribute information;
Transmitting the recommended information for recommending the read explanation of the history event as a candidate for citation to the user's own history to the terminal device of the user.

Images