Retrieval history storage system

The present invention relates to a system in which a search history in which a user uses a search engine is stored in a server and used by the user.

Conventionally, when a general user searches for a place (hereinafter, simply referred to as "site") where information on the Internet (for example, a web page of a website, an image file, a video file, etc.) is located, for example, Google, Yahoo, Goo In many cases, keyword search (search by entering a search word) is performed using a search engine provided on homepages such as Infoseek. Normally, the search database of a search engine stores the title (name), URL, summary (for example, a part of the text in the automatically collected HTML file), etc. as the site information collected from the Internet. In the list of search results that the user browses with a browser, these titles, URLs (these have links to the site), an outline, and the like are displayed. The user can easily access (visit) the desired site by simply clicking the link to the desired site from the list.

Of the sites visited in this way, in order to collect and save what you need or like, you usually use the bookmark (favorite) registration function provided in your browser. This allows you to save a shortcut file to the site locally on your computer with a simple operation, and after that, you can access it from the list of saved bookmarks (favorites).

However, in the current search engine, the number of search results is enormous in many cases. Therefore, it is not realistic to bookmark all the visited sites (including those that are only temporarily needed) because it is troublesome and difficult to browse later. On the other hand, if you do not keep a browsing history, if you want to visit the site you visited before, you have to search again with the search engine, and the search database is updated from time to time, so it is the same as before You may not always be able to find the site.

In response to this problem, for example, in "Personalized search" of Google (Non-Patent Document 1), when a registered user is logged in and uses a search engine, the search conditions (search words) entered by the user and the search are performed. It automatically saves the information of the visited site from the result list and provides a service that allows users to browse their search history with a browser.

<nplcit num="1"><text>http://www.google.co.jp/</text></nplcit>

<p> In the conventional search history saving service, all the search history is automatically saved. Therefore, information that the user does not want to collect (for example, information for adults, information including words that the user does not want, etc.) is also saved as a history. Therefore, unnecessary history must be manually deleted by the user later on the browser. Furthermore, if the search history is saved on the server, the user can share the search history with other users (for example, publish his / her search history to other users or view the search history of other users). It is possible to provide to. In this case, it is particularly necessary to have a system in which unnecessary search history is not collected.</p>

<p> In order to solve the above problems, the present invention is a search history storage system in which a user terminal stores a search history using a search engine in a server, and stores the conditions for storage restriction of the search history. When the search word of the search condition is received from the setting storage means and the user terminal, the search word storage means for storing the search word in the storage means as a search history according to the stored storage restriction condition, and the user. Upon receiving the access to the search result site from the terminal, the site history storage means that stores the access information to the site in the storage means as the search history according to the stored storage restriction conditions, and the user terminal. The search history storage system is provided with a search history transmission means for transmitting a page displaying the search history of the user terminal to the user terminal in response to the request of the user terminal. Further, the user terminal may be provided with a storage setting means for transmitting a page for storage setting to set the storage restriction condition and storing the setting in the storage setting storage means. Further, the storage restriction condition of the storage setting storage means includes a prohibited word, and the search word storage means and the site history storage means do not store the search condition and the site information including the prohibited word. Good. Further, the storage restriction condition of the storage setting storage means includes a prohibited URL, and the search word storage means and the site history storage means do not store the search condition and the site information including the prohibited URL. Good. Further, the search history transmitting means may be characterized in that the user terminal transmits the editing page of the search history and updates the corresponding item of the search history of the storage means with the edited contents received from the user terminal. Further, the search history transmitting means may further be characterized in that, in response to a request from the user terminal, a page for viewing the search history of another user terminal is transmitted. Further, the above-mentioned storage setting means sends a page for application for storage setting to the user terminal of the user to specify another user who wants to set the condition of storage restriction, and receives the application for storage setting. , The feature is that the relationship between the user and the designated other user is determined, and when the relationship is constant, the page for the storage setting of the other user is transmitted to the user terminal of the user. May be. Further, when the above-mentioned storage setting means receives the storage setting application, it transmits a consent page to the user terminal of the other user, and when the consent is received from the user terminal of the other user, the user's terminal It may be characterized by transmitting the page for the storage setting of the other user to the user terminal. Further, the present invention is a search history saving method in which a user terminal stores a search history using a search engine in a server, and stores search history storage restriction conditions, and the search conditions can be obtained from the user terminal. When the search word is received, the search word storage step of storing the search word in the storage means as the search history according to the stored storage restriction conditions and the access to the search result site from the user terminal are received. Then, the site history saving step of storing the access information to the site in the storage means as the search history according to the stored storage restriction conditions, and the search of the user terminal according to the request from the user terminal or the like. This is a search history storage method including a search history transmission step of transmitting a page displaying the history to the user terminal. A program for causing a computer to function each means of the search history storage system described in any of the above is also the present invention.</p>

<p> According to the search history storage system of the present invention, the search history (in the present embodiment, the search condition and the history of the site accessed (visited) from the search result) is automatically saved. At that time, the user can freely specify prohibited words, prohibited URLs, etc. and impose storage restrictions, so do not collect unnecessary information or information that you do not want to store in a simple and detailed manner. Can be done. The content of the storage restriction can be freely determined by the system according to the necessity. In addition, the user can effectively use the collected search history by adding information (for example, comments, evaluations, etc.) to the search history, classifying and organizing by labels, and the like. The content of the information to be added to the search history can be freely determined by the system according to the necessity. Moreover, since the search history is stored in the server, the search history can be easily shared with other users as a system. Being able to perform the above-mentioned storage restrictions and editing is especially useful when sharing the search history.</p>

Hereinafter, an example of an embodiment of the search history storage system of the present invention will be described with reference to the drawings. (1) First, an outline of the system of this embodiment will be described (Figs. 1 to 3). (2) Next, a web page for the user to use the search history will be described (Fig. 4). (3) Next, the setting of the storage limit will be described (Figs. 17 to 19). (4) Next, saving the search history will be described (Figs. 5 to 7). (5) Finally, the transmission of the search history list page to the user terminal and the editing of the search history by the user will be described (Figs. 8 to 16).

(1. System Overview) First, the outline of the system of this embodiment will be described with reference to the system configuration diagrams and database items of FIGS. 1 to 3. FIG. 1 is a diagram showing an example of a system configuration using the search history storage system of the present embodiment.

(1-1. User Terminal) In FIG. 1, the user terminal 110 is a terminal such as a personal computer used by the user, and is connected to the server 130 through the Internet 120. The browser 112 is conventional conventional browser software installed on the user terminal 110. The user uses the search system 140 (conventional search engine) of the server 130 and the search history storage system 150 of the present embodiment on each page transmitted from the server 130 and displayed on the browser 112 of the user terminal. Each page transmitted to the user terminal 110 will be described in detail later. The cookie 114 is a conventional cookie, and includes information for the server 130 to identify the user terminal 110. For example, the Cookie 114 is transmitted from the server 130 when the user terminal 110 first accesses the top page of a search engine or the like, and is stored in the user terminal 110. After that, every time the user terminal 110 accesses the server 130, the cookie 114 is automatically transmitted from the user terminal 110 to the server 130. As a result, the server 130 can identify the user (user terminal 110) without the user having to perform so-called user registration and login. Instead of the above-mentioned cookie, the user may be registered and the user may be identified by logging in from the user terminal 110.

(1-2. Search system) In the server 130, the search system 140 provides the user with a conventional normal search engine (for example, a search engine provided on the top page of Google, Yahoo, Goo, Infoseek, etc.). It is a system. The search database 142 is the above-mentioned conventional search database, and stores information (name (title), URL, outline, etc.) of the site collected on the Internet. Further, in the present embodiment, these sites are stored with a type (for example, a web page, an image file, a video file, a blog (top page), a news article (web page), etc.). The user can search by inputting a search word for all types, and can also search by selecting a type of search target and inputting a search word. It should be noted that such a search engine is a conventional technique. When the user inputs a search condition on the search page displayed on the browser 112 of the user terminal 110 to perform a search, the search process 144 searches the search database 142 and searches the search result site name, URL, and so on. It is a program that performs a process of transmitting a page displaying a list of outlines and the like to a user terminal 110.

(1-3. Search history storage system) The search history storage system 150 is the search history storage system of the present embodiment, and is a system that stores the history of searches performed by the user with a search engine. In the present embodiment, the search conditions and the history of the sites accessed (visited) from the search results are saved as the search history. When saving the search history, it is determined whether or not the search history can be saved according to the storage restriction conditions set by the user. It also allows the user to browse the search history so that the user can delete or edit the search history.

In the search history storage system 150, the search word database 151 is a database that stores search words and the like of search conditions entered by the user. The search word database 151 is stored in the search word storage process 161. The processing procedure of the search word saving process 161 will be described in detail later. FIG. 2 (a) is a diagram showing an example of the main items of the search word database 151. The "user ID" is an ID that uniquely identifies a user. As described above, in this embodiment, the information stored in Cookie 114 is used. The "search No." is a number uniquely assigned to the user's search. The "search word" is an input search word. The "search type" is the selected type (for example, the above-mentioned web page, image, video, blog, news, etc.). In addition, the user can repeatedly perform a re-search from the search history under the same search conditions. The "number of searches" is the number of times the user has performed the search. The "last search date and time" is the date and time when the user last performed the search.

The site history database 152 is a database that stores information on sites visited by the user from the search result list page. Registration in the site history database 152 is performed in the site history saving process 162. The processing procedure of the site history saving process 162 will be described in detail later. FIG. 2B is a diagram showing an example of the main items of the site history database 152. The "user ID" is the above-mentioned user ID (information stored in Cookie 114 in the present embodiment). The "search number" is information indicating from which search result the site was browsed, and corresponds to the search number of the search word database 151. The "site URL", "site name", and "site outline" are the name (title), URL, and outline of the site stored in the search database 142, respectively. In addition, the user can repeatedly visit the same site from the search history. The "access count" is the number of times the user has visited the site. The "last visit date and time" is the date and time when the user last visited the site.

Further, the "comment", "evaluation item ID", "evaluation", and "label ID" are items to which the user can add information later to the site history stored in the site history database 152. The comment is a user's comment on the site. The label is a label that classifies the site, and is, for example, "news", "recommended", or the like. In this embodiment, the user can freely create and edit labels. The created / edited label is registered in the label database 154 by the label registration / update process 165. The creation and editing of labels will be described in detail later. An example of the main items in the label database 154 is shown in Figure 3 (a). The "user ID" is the above-mentioned user ID (information stored in Cookie 114). The "label ID" is an ID uniquely attached to the label. The "label name" is, for example, a label name such as "news" or "recommended".

The evaluation is a user's evaluation of the site, and consists of evaluation items (for example, "interesting", "cheapness", etc.) and evaluations in those evaluation items (for example, 5-grade evaluation). In this embodiment, the user can freely create and edit evaluation items. The created / edited evaluation item is registered in the evaluation item database 155 by the evaluation item registration / update process 166. The creation and editing of evaluation items will be described in detail later. An example of the main items of the evaluation item database 155 is shown in Fig. 3 (b). The "user ID" is the above-mentioned user ID (information stored in Cookie 114). The "evaluation item ID" is an ID uniquely assigned to the evaluation item. The "evaluation item name" is, for example, an evaluation item name such as "interesting" or "cheap". Although the above-mentioned functions for adding comments, labels, and evaluations are not essential functions in the present embodiment, the comments and evaluations are particularly useful when the search history is disclosed to other users. Labels are also useful for organizing a large number of search histories in an easy-to-read manner.

Returning to FIG. 1, the search history transmission process 163 is a process of creating a web page displaying a list of the user's search history and transmitting it to the user terminal 110 in response to a request from the user or the like. The user can browse the search history on the browser 112 and delete or edit the search history. When the user deletes or edits the search history, the search history (search word database 151 and site history database 152) is updated with the contents. Each page transmitted to the user terminal 110 will be described in detail later.

The storage setting database 153 is a database that stores settings such as storage restrictions for each user (user terminal 110). In this embodiment, the user can set the contents such as storage restrictions. The save setting process 164 is a process of registering / updating the user's settings in the save setting database 153. FIG. 2 (c) is a diagram showing an example of the main items of the storage setting database 153. The "user ID" is the above-mentioned user ID (information stored in Cookie 114). The "saveability flag" is a flag indicating whether or not to save the search history. The "save pause flag" is a flag indicating whether or not the save is paused. The "storage restriction information (prohibited word)" is a keyword specified by the user as a prohibited word (information including this word is not saved as a search history). In this embodiment, a plurality of prohibited words can be specified. "Retention restriction information (prohibited URL)" is a URL (or a part of the URL) specified by the user as a prohibited URL (information including this URL is not saved as a search history). In this embodiment, a plurality of prohibited URLs can be specified. "Save restriction information (adult genre saveability flag)" is information that the search engine provider determines to be an adult genre (for example, information including keywords and URLs for adults specified by the search engine provider). It is a flag indicating whether to save as a search history.

The "history capture flag" is a flag that indicates whether or not the history of searches performed by a registered user in the logged-off state when a search engine provider has registered a user will be inherited when logging on thereafter. is there. The "number of items displayed per page" is an item indicating how many records are displayed per page in a list of search histories displayed on the browser 112 of the user terminal 110.

The server 130 does not have to be one server, and for example, the search system 140 and the search history storage system 150 may be divided into different servers. In addition, the database and processing programs in each system may be stored separately on a separate server.

(2. Configuration of user-only page) Next, referring to Fig. 4, the user searches and uses the search history (viewing / deleting / editing the search history and setting storage restrictions). Web page (hereinafter referred to as user-only page) will be explained. As described above, the search history transmission process 163 performs the creation of each page of the search history and the transmission to the user terminal 110. FIG. 4 is an example of a user-only page of this embodiment. As described above, the server 130 identifies the user terminal by the cookie 114 transmitted from the browser 112 when accessed from the user terminal 110. Therefore, the search history of the user and the like can be read from each database and displayed on the user-only page.

In the user-only page 400, the search box 410 is an area where the user searches. Click the "Search History" tab 413 on the far right of the tabs lined up at the top of the search box 410 to display a list of all search history (search conditions and site history corresponding to that search) for that user. Transition to the site history list page (displayed in the main display area 480 in this embodiment. The same applies thereafter). The site history list page will be described later with reference to the example of the site history list page in FIG. Here, when the user enters a search keyword in the search text box 411 and clicks the "search" button 412, the search word database 151 and the site history database 152 are searched, and the site list page listing the search results is displayed. Transition to. In the example of FIG. 4, the "Search history" tab 413 is provided, but instead of the "Search history" tab 413, the page displayed by clicking each tab (for example, the "Image" tab) is displayed. A link for transitioning to the user's search history page may be pasted on the page displayed by clicking). That is, the display is not limited to the "Search history" tab 413, and each site may display text (text to which the URL is pasted) for prompting the transition to the search history page.

In addition, the other tabs at the top of the search box 410 (Google search, Infoseek search, directories, blogs, images, videos, software, news in the example in Figure 4) correspond to the types of search database 142. When the user clicks the desired tab and enters the keyword in the search text box 411 to perform a search, the search process 144 uses the selected type and the entered keyword (search word) as search conditions to search the search database. 142 is searched, and the search result transitions to the page listing. An example of the search result page will be described later with reference to the example of the search result page of FIG.

The search history setting area 420 is an area displaying a link to a page or the like for which the user sets a storage restriction. The "pause auto-save" link 421 is a link that temporarily suspends the saving of the search history. Specifically, when the user clicks the "Pause automatic save" link 421, the save pause flag of the save setting database 153 is turned on (cannot be saved) and the subsequent search history is not saved. When autosave is paused, the display of "Pause autosave" link 421 changes to "Resume autosave". When the user clicks the "Resume automatic save" link, the save pause flag of the save setting database 153 is turned off (save is possible), and the subsequent search history is saved. The "search history setting" link 422 is a link for transitioning to a page in which the user sets storage restrictions and the like. The search history setting will be described in detail later with reference to the search history setting pages of FIGS. 17 to 19.

The left navigation 430 is a part that displays the user's recent search history together with a link to a list display page and the like. The left navigation 430 consists of a calendar display area 440, a recent search word display area 450, a site list display area 460, and a bookmark registration box 470. The search history is displayed in the calendar format in the calendar display area 440. The calendar date corresponds to the last search date and time in the search word database 151. In addition, the number of site histories on that day is displayed in different colors to make it easier for users to see. When the user clicks the date link, the site transitions to the site history list page that lists the search history (search conditions and the site history corresponding to the search) for that day.

Recently, in the search word display area 450, user searches are displayed in chronological order (here, 4 items are displayed as an example). Here, the display of "Cookie-5 times (8)" is, from the left, the search word, the number of searches (total number of searches for all types by the same search word), and the number of site histories visited from the search (same search). The total number of site histories for all types by word) is shown. Clicking on a search word will take you to the site history list page, which lists the corresponding site history. Click the "more" link 451 to move to the search word list page that lists the searches. The search word list page will be described in detail later with reference to FIG.

In the site list display area 460, the user's site history is displayed in the order of frequently used labels (label order list 461) and in the order of frequently used evaluation items (evaluation item order list 463). ing. Clicking the "Site list" link will take you to the site history list page, which lists all the user's search history (search conditions and site history corresponding to that search). Clicking each label name displayed on the label list display unit 461 will take you to the site history list page that displays a list of site histories with the corresponding labels. If you click the "more" link 462, you will be taken to the label edit page that displays the label list. The label editing page will be described in detail later with reference to FIG. Clicking the name of each evaluation item displayed on the evaluation item list display unit 463 will take you to the site history list page that displays a list of site histories with the corresponding evaluation. If you click "More" 464, you will be taken to the evaluation item edit page that displays the evaluation item list. The evaluation item edit page will be described in detail later with reference to FIG.

The bookmark registration box 470 is an input box that allows the user to register the site by himself / herself. Enter the desired URL in the URL input text box 471 and click the "Register" button 472 to register the URL in the site history database 152. At this time, the label "bookmark" prepared in advance by the system is attached. Editing of the site registered here (addition of site name, comments, evaluation, etc.) is performed on the site history editing page in the same way as normal site history. The site history edit page will be described in detail later with reference to the example of the site history edit page in FIG.

(3. Setting of storage limit) Next, the setting of the storage limit by the user will be described with reference to each page of FIGS. 17 to 19. As described above, when the "search history setting" link 422 is clicked in FIG. 4, the user transitions to the search history setting page for setting the storage restriction. An example of the search history setting page is shown in FIG. The user sets the save method of the search history, the number of displayed items, etc. in each field of "Search history setting" 1710, and the setting contents are stored in the save setting database 153.

In the detailed setting field 1711, "Save search history" is a check box for setting whether to save the search history in the search word database 151 and the site history database 152. If you check it and click the "Save settings" button 1714, the save availability flag of the save setting database 153 will be updated to "Saveable" and the subsequent search history will be saved. Also, if you uncheck it and click the "Save settings" button 1714, the save enable / disable flag will be updated to "Cannot save" and the subsequent search history will not be saved. In addition, "importing the previous search history at login" is a search saved when the registered user is not logged in when the provider of the search history saving system of the present embodiment has also registered as a user. This is a check box to set whether to inherit the history after logging in. The settings are stored in the history import flag of the save setting database 153.

The display number setting column 1712 per page is a column for setting the number of search history and the like to be displayed on one page in the search history list page (search word list page and site history list page) and the like. The settings are stored in the number of items displayed per page in the save setting database 153.

The filtering setting field 1713 is a field for setting storage restrictions in detail. If you check the "Do not save search words and browsing sites that include the specified words" check box, the search history that includes the registered words will not be saved after that. In this embodiment, as an example, prohibited words (prohibited words) and prohibited URLs (prohibited URLs) can be registered. Clicking the "Prohibited word / URL setting" link will take you to the prohibited word setting page shown in Fig. 18 and the prohibited URL setting page shown in Fig. 19. To register a prohibited word, enter the prohibited word in the text box of the prohibited word input field 1810 on the prohibited word setting page shown in FIG. 18 and click the "Register" button. The registered prohibited words are stored in the storage restriction information (prohibited words) of the storage setting database 153. The prohibited words that have already been registered are displayed in the prohibited word list 1830. To delete a prohibited word, check the check box on the left side of the prohibited word list 1830 and click the "Delete" button in the prohibited word deletion column 1820. If you click "Check All" here, all prohibited words will be checked. To register the prohibited URL, enter the prohibited URL in the text box of the prohibited URL input field 1910 on the prohibited URL setting page shown in FIG. 19 and click the "Register" button. The registered prohibited URL is stored in the storage restriction information (prohibited URL) of the storage setting database 153. The prohibited URLs that have already been registered are displayed in the prohibited URL list 1930. To delete a prohibited URL, check the check box on the left side of the prohibited URL list 1930 and click the "Delete" button in the prohibited URL deletion field 1920. If you click "Check All" here, all prohibited URLs will be checked.

Returning to the search history setting page 1700 in FIG. 17, the bookmark import area 1720 is an area where the user can easily add the site bookmarked by the function of the browser 112 to the site history of the present embodiment. To import a bookmark, enter the path to the bookmark file in the path input field 1721 and click the "Import" button 1723, and the bookmark information (URL, site name, etc.) will be registered in the site history database 152. In this embodiment, a label "bookmark" prepared in advance by the system is attached. Click the Browse button 1722 to display a file selection dialog box where you can easily specify the path to the bookmark file.

(4. Saving the search history) Next, saving the search history will be described with reference to the search result page of FIG. 5 and the flowcharts of FIGS. 6 to 7. The search history is saved according to the storage limit set by the user in (3. Setting the storage limit) above.

(4-1. Saving search conditions) As described above, when the user performs a search using the search system 140 on the user-only page 400 in FIG. 4, the search process 144 searches the search database 142 and searches. The result list page (FIG. 5) is transmitted to the user terminal 110. At this time, the search word saving process 161 saves the keyword (search word) or the like input as the search condition in the search word database 151.

Figure 5 shows the search results when the user selects the type "Google Search" in the tab at the top of the search box 410 and enters the keyword (search word) "Hattori-kun" in the search text box 411. This is an example of a list page. In the present embodiment, the search result list page is displayed in the main display area 480 of the user-only page 400 of FIG. 4 described above. On the search result list page 500, information such as the site name 511, the site outline 512, and the site URL 513 of the site stored in the search database 142 is displayed for each search result 510 in the search result list. Further, the related category 520 or the like may be displayed on the search result page. If you want to move to another page of the search result page, click the number of pages displayed on the page navigation link 530. These are the functions of conventional search engines.

FIG. 6 is a flowchart showing an example of the flow of the search word saving process 161. When the user performs a search with a search engine and receives the search condition input from the user terminal 110 (S610), it first determines whether the user is a user who can save the search history (S620). Specifically, the save enable / disable flag and the save pause flag of the save setting database 153 corresponding to the user ID (cookie) of the user are referred to. If either or both of the save enable / disable flag and the save pause flag are "unable to save" (No in S620), do nothing (without registering the search in the search word database 151). To finish. On the other hand, when both the save enable / disable flag and the save pause flag are "saveable" (Yes in S620), it is determined whether the search condition (search word) is subject to the save restriction (S630). ). Since the search condition in the present embodiment is the search word + type, it is determined whether the search word is subject to storage restrictions. That is, it is determined whether or not the search word corresponds to the storage restriction information (prohibited word) by referring to the storage setting database 153 corresponding to the user ID (cookie) of the user. Further, when the storage restriction information (adult genre saveability flag) of the save setting database 153 cannot be saved, it is determined whether the search word corresponds to the adult genre determined in advance by the search engine provider.

If it is determined that the search word is subject to storage restrictions (Yes in S630), the process ends without doing anything (without registering the search in the search word database 151). On the other hand, if the search word is not subject to storage restrictions (No in S630), the search condition is registered in the search word database 151 and the process ends (S640). Specifically, in the present embodiment, each item of the search word database 151, that is, the user ID, the search No., the search word, the search type, the number of searches, and the last search date and time is stored. In the example shown in FIG. 5 above, "Hattori-kun" is stored in the search word and "Web search" is stored in the search type. In addition, "1" is stored in the number of searches, and the current search date and time is stored in the last search date and time. For example, if "Hattori-kun" is subject to storage restrictions, it will not be stored in the search word database 151.

(4-2. Saving the site history) When the user visits the site from the list of search results (click the name 511 or URL 513 of the site that the user wants to see in the list of search results in Fig. 5 above), Along with jumping to the site, the site history saving process 162 saves the information of the site in the site history database 152.

FIG. 7 is a flowchart showing an example of the flow of the site history saving process 162. When receiving the click of the link to the site from the search result list page (Fig. 5 above) (S710), it first determines whether the user is a user who can save the search history (S720). Specifically, in the present embodiment, the save enable / disable flag and the save pause flag of the save setting database 153 corresponding to the user ID of the user are the same as the search word save process 161 described above with reference to FIG. If it cannot be saved (No in S720), do nothing (without registering the site in the site history database 152) and end the process. On the other hand, if it can be saved (Yes on S720), it is determined whether the site is subject to storage restrictions (S730). Specifically, in the present embodiment, the information of the site (site name, URL, site outline, etc. registered in the search database 142) is referred to by referring to the storage setting database 153 corresponding to the user ID of the user. Information) contains storage restriction information (prohibited words) and storage restriction information (prohibited URL).

Further, as in the search word saving process 161 described above with reference to FIG. 6, if the saving restriction information (adult genre saving possibility flag) cannot be saved, the site is determined in advance by the search engine provider. Determine if it corresponds to the adult genre you are in. If it determines that the site is subject to storage restrictions (Yes for S730), it does nothing (without registering the site in the site history database 152) and terminates the process. On the other hand, if the site is not subject to storage restrictions (No in S730), the site is registered in the site history database 152 and the process ends (S740). Specifically, in the present embodiment, the user ID, search number (corresponding to the search number of the search word database 151), and site URL of the site history database 152 described above with reference to FIG. 2 (b). , Site name, site outline, number of accesses (enter 1 as the initial value), last visit date and time (date and time of this visit) are memorized.

(5. Sending search history and editing by user) Finally, referring to each page shown in Fig. 8 to Fig. 16, we will explain how to send the search history list page etc. to the user terminal and edit the search history by the user. To do. The search history transmission process 163 performs the process of transmitting each page to the user terminal 110 and saving the user's edits in the database.

(5-1. Sending the site history list) As described above, on the user-only page 400 in Fig. 4, the user can search the search history in the search box 410, click the date on the calendar display unit 430, and click "Site". Clicking link 460 in "List", clicking "More" link 462 in label order list 461, clicking "More" link 464 in evaluation item order list 463, etc., displayed a list of target search histories. Transit to the site history page.

Figure 8 is an example of the site history list page. FIG. 8 shows an example in which the search history to be displayed is displayed in a list for each search condition. The display items and display order are examples. On the site history list page 800, the site list display area 820 displays the search history (search conditions and the site history corresponding to the search) to be displayed in the order of the latest search date of the search word database 151. There is. The date display field 821 and the search word display field 822 display the last search date and the search word of the search word database 151, respectively. Clicking on a search word will take you to the site history list page that displays all the site history (including site history that was not displayed) that corresponds to that search (same search number). In the storage type display field 823, the search type of the search word database 151 (Web search in the example of FIG. 8) is displayed. In the search count display field 824, the search count of the search word database 151 is displayed. When the "research" link 825 is clicked, the search process 144 searches the search database 142 again with the same search conditions, and transitions to the search result page (Fig. 5). At the same time, the search history transmission process 163 updates the last search date and time of the search word database 151 and increases the number of searches by 1.

In the site history display field 830, the site history to be displayed is displayed, for example, in ascending order of the site name. The site name, site outline, and site URL of the site history database 152 are displayed in the site name display column 831, the site outline display column 832, and the site URL display column 833, respectively. The last visit date and time and the number of accesses of the site history database 152 are displayed in the display column 834 such as the last visit date. Here, if you click the site name or site URL, you will be redirected to that site, the last visit date and time of the site history database 152 will be updated, and the number of accesses will be increased by 1. If you click "Edit" on the right side of the site name 831, you will be taken to the page for editing the site history (site edit page in Fig. 12). Editing the site history will be explained in detail later.

In the label display field 835, the label name corresponding to the label ID of the site history database 152 is read from the label database 154 and displayed. Clicking the label name will take you to the site history list page that lists the site history with that label. In the evaluation display column 836, the evaluation item name corresponding to the evaluation item ID of the site history database 152 is read from the evaluation item database 155 and displayed, and the evaluation of the site history database 152 is displayed by, for example, the number of stars. Clicking the evaluation item name will take you to the site history list page that displays a list of site histories that have been evaluated for that evaluation item. The comment of the site history database 152 is displayed in the comment display field 837. The comment is displayed up to a predetermined number of characters, for example, and the full text is displayed by clicking the "more" link 838.

Also, in the navigation bar 810, click the "Check All" checkbox 811 to check all the site history checkboxes displayed on the current page. The "Delete" button 812 is a button for deleting the checked site history from the site history database 152. The site number display column 814 indicates the number of site histories to be displayed and the number of the site currently displayed. The "next 10" link 814 is a link that transitions to the next page of the site list. From the second page onward, you should also display the "previous 10" links. The number of items displayed on one page follows the number of items displayed per page of the save setting database 153. The display target selection link 815 is a link for selecting the type of site history to be displayed, and can be selected from "all" and each type. The display number selection link 816 is a link for temporarily changing the number of site histories displayed on one page.

The "Display list for printing" button 813 is a button for transitioning to the page displaying the site history selected by the check box for printing. In addition, instead of the page transition, for example, another window may be started and displayed. Figure 9 shows an example of a page for printing site history. In the site history print page 900, the title of the print page (site list in the example of FIG. 9) is displayed in the page title display field 901. In addition, necessary information such as the date display field 902 and the search word display field 903 should be displayed in an easy-to-read manner. In the site history display field 910, for example, for each site history, the site name display field 911 is the site name, the site URL display field 912 is the site URL, the site summary display field 913 is the site outline, and the last visit date. The last visit date and time and the number of accesses should be displayed in the equal display column 914, the label name in the label display column 915, the evaluation items and evaluations in the evaluation display column 916, and the comments in the comment display column 917 in a tabular format, etc. ..

(5-2. Sending a list of search conditions) Further, in FIG. 4 above, when the user clicks "more" 451 of the search word 450 recently, the page transitions to the search word list page of FIG. In the search word list page 1000 of FIG. 10, the navigation bar 1010 is the same as the navigation bar 810 of the site history list page described in FIG. 8, and the selected search condition is deleted, the display target is selected, and the number of items to be displayed is set. , This is the area where the print page of the selected search condition is displayed. FIG. 11 is an example of a page for printing a search word. In the page title display field 1101, the title of the page for printing (searched word list in the example of FIG. 11) is displayed. In the search word list display field 1110, for example, the search word is displayed in the search word display field 1111, and the number of site histories corresponding to the search (same search number) is displayed in the site history number display field 1112. The search type is displayed in the search type display field 1113, and the last search date and time is displayed in the search date and time display field 1114 in a tabular format or the like for easy viewing.

Returning to the search word list page 1000 in FIG. 10, the search condition list area 1020 is an area for displaying a list of search conditions. The last search date and the search word of the search word database 151 are displayed in the date display field 1031 and the search word display field 1032 of the search condition display field 1030, respectively. Clicking on a search word will take you to the site history list page, which lists the site history corresponding to that search. In the search count display field 1033, the search count of the search word database 151 is displayed. In the site history number display field 1034, the number of site histories corresponding to the search is displayed. In the search type display field 1035 and the search date / time display field 1036, the search type and the last search date / time of the search word database 151 are displayed, respectively.

(5-3. Editing the site history) In addition, when the user clicks "Edit" on the right side of the site name display field 831 on the site history list page in Fig. 8 above, the site transitions to the site history editing page in Fig. 12. .. On the site history edit page 1200, clicking the "Delete this history" button 1210 deletes this site history from the site history database 152. The basic information edit input area 1220 is an area for editing basic information (site name, site URL, site outline) of the site history. The site name of the site history database 152 is displayed in the site name edit input field 1221 and can be edited by the user. The site URL of the site history database 152 is displayed in the site URL edit input field 1222, and can be edited by the user. The title and URL are required items in the site history and cannot be left blank. The site outline of the site history database 152 is displayed in the text box of the site outline edit input field and can be edited by the user. If you edit these basic information and click the "Save" button 1270, the site history database 152 will be updated with the entered contents.

Arbitrary information editing input area 1230 is an area for adding and editing arbitrary information (label, evaluation, comment in this embodiment) of the site history. Labels are set in the label edit input area 1240. In the label input field 1241, the labels registered in the label database 154 are displayed in the list box, so select the label you want to attach. Labeling adds the label ID to the site history database 152. If you want to add a new label (not yet registered in the label database 154), enter the new label name in the text box of the new label registration field 1242 and click the "Add" button to add the label database. Register the label in 154 and add the label ID of the label to the site history database 152. In the label list display field 1243, the labels attached to this site history are listed. Click the "x" button to the left of each label in the label list display field 1243 to remove the label from the site history (delete the label ID of the site history database 152).

In addition, new additions and edits of labels are performed on the label list page of FIG. 13 and the label edit page of FIG. The added / edited label is registered / updated in the label database 154 by the label registration / update process 165. Clicking "More" 462 in FIG. 4 transitions to the label list page in FIG. Here, if you want to create a new label, enter the label name in the new label input text box 1311 in the new label registration area 1310, and click the "Add" button 1312. In addition, the label list area 1330 displays a list of labels registered in the label database 154. The label name of the label database 154 is displayed in the label name display field 1331. Clicking the label name will take you to the site history list page that lists the site history with that label (site history with the label ID of that label). In the site history number display field 1332, the number of site histories with the label is displayed. The display order selection link 1323 is a link that specifies whether to display the label list 1330 in the order of the number of site histories or the label name.

To delete a label, check the check box to the left of each label name in the label list and click the "Delete" button 1322. If you click "Check All" 1321, all labels in the label list will be selected. Labels can be edited on the label edit page shown in Fig. 14, which is transitioned by clicking the "Edit" link 1333 on the right side of each label name in the label list. On the label edit page 1400, the current label name is displayed in the label display field 1410 before change. If you want to change the label name, enter the changed label name in the changed label input field 1420 and click the "Save" button 1430. Click the Delete button 1440 to delete the label from label database 154.

Returning to the site history edit page 1200 in FIG. 12, the evaluation items are set in the evaluation edit input area 1250. In the evaluation input field 1251, the evaluation items registered in the evaluation item database 155 are displayed in the list box. Select the evaluation item you want to attach and evaluate from the evaluation selection list box (for example, 5 levels from 1 to 5). ) Is selected. Then, the evaluation item ID and the evaluation are added to the site history database 152. If you want to give an evaluation with a new evaluation item (not yet registered in the evaluation item database 155), enter the new evaluation item name in the text box of the new evaluation item registration field 1252 and click the "Add" button. Then, the evaluation item is registered in the evaluation item database 155, and the evaluation item ID and the evaluation of the evaluation item are added to the site history database 152. In the evaluation list display column 1253, the evaluation items of the evaluation attached to this site history are listed. Click the "x" button on the left side of each evaluation item in the evaluation list display column 1253 to remove the evaluation from the site history (delete the evaluation item ID and evaluation of the site history database 152).

In addition, new evaluation items are added and edited on the evaluation item list page of FIG. 15 and the evaluation item editing page of FIG. The added / edited evaluation item is registered / updated in the evaluation item database 155 by the evaluation item registration / update process 166. Clicking "More" 464 in Fig. 4 will take you to the evaluation item list page in Fig. 15. Here, if you want to create a new evaluation item, enter the evaluation item name in the new evaluation item input text box 1511 in the new evaluation item registration area 1510, and click the "Add" button 1512. Further, in the evaluation item list area 1530, the evaluation items registered in the evaluation item database 155 are displayed in a list. The evaluation item name of the evaluation item database 155 is displayed in the evaluation item name display column 1531. Clicking the evaluation item name will take you to the site history list page that displays a list of site history with that evaluation item (site history with the evaluation item ID of that evaluation item). In the site history number display column 1532, the number of site histories with the evaluation item is displayed. The display order selection link 1523 is a link that specifies whether to display the evaluation item list 1530 in the order of the number of site histories or the name of the evaluation item.

To delete an evaluation item, check the check box to the left of each evaluation item name in the evaluation item list and click the "Delete" button 1522. Also, if you click "Check All" 1521, you can select all the evaluation items in the evaluation item list. To edit the evaluation items, click the "Edit" link 1533 on the right side of each evaluation item name in the evaluation item list to move to the evaluation item edit page in Fig. 16. On the evaluation item edit page 1600, the current evaluation item name is displayed in the evaluation item display column 1610 before change. If you want to change the evaluation item name, enter the changed evaluation item name in the changed evaluation item display field 1620 and click the "Save" button 1630. Click the "Delete" button 1640 to delete the evaluation item from the evaluation item database 155.

Returning to the site history editing page 1200 in FIG. 12, the comment editing input field 1260 is a text box for inputting / editing a comment. If you enter any of these information and click the "Save" button 1270, the site history database 152 will be updated with the entered information. Although the above-mentioned arbitrary information on the site history is not essential to the present embodiment, comments and evaluations are particularly useful when the search history is disclosed to other users (also viewed by other users). Labels are also useful for organizing a large number of search histories in an easy-to-read manner.

In the above description, the case where the search history is transmitted only to the user (user terminal) himself / herself for viewing / editing has been described as an example, but the search history of another user may also be browsed. This allows the user to share the search history. In this case, the user registers the user in the server 130 in advance, logs in with the user ID and password, and uses the search system 140 and the search history storage system 150 of the present embodiment. The search history is saved corresponding to the user ID. As a result, the search history of other users can be sent, for example, in response to a request from the user, or the system automatically determines and sends (for example, the evaluation / comment of another user for the same search history is sent. , Send the search history of users who have something in common with the age and registered profile, etc.).

In the above, the case where the user sets the save setting only for his / her own search history has been described, but for example, the case where the parent wants to limit the save for the child's search or the boss wants to limit the save for the subordinate's search. Be done. Hereinafter, as a second embodiment of the search history storage system of the present invention, when a certain user and another user have a specific relationship (parent-child relationship, boss / subordinate relationship, etc.), that user (parent or A search history saving system that can set the saving settings of the other user (children and subordinates) by application from the boss) will be described. In this second embodiment, the user needs to be registered in the server 130 as in the case of sharing the search history described above. Therefore, a user database in which users are registered is further prepared on the server 130 in the system configuration diagram of FIG. Further, here, each process of the second embodiment will be described as being implemented in the above-mentioned storage setting process 164.

FIG. 20 is a diagram showing the main items of the user database. The "user ID" is a unique ID for the user and is given at the time of user registration. The "password" is a password for the user to use the system of the present embodiment. The user enters these user IDs and passwords to log in to the server 130, and uses the search system 140 and the search history storage system 150 of the present embodiment. The "name", "date of birth", "address", and "telephone number" are the user's name, date of birth, address, and telephone number, respectively. Further, profiles such as hobbies and tastes may be registered in the user database. The "email address" is the user's email address. The "configurable user ID" is a user ID of another user (for example, a child or a subordinate) whose save setting can be made by the user (for example, a parent or a boss). The association between the user ID of the parent or boss and the user ID of the child or subordinate may be stored in a database different from the user database.

Hereinafter, two mechanisms (method 1) and (method 2) will be described as specific examples of the second embodiment of the search history storage system of the present invention. These mechanisms are implemented in the above-mentioned storage setting process 164, but either mechanism may be implemented or both may be implemented depending on the needs of the system.

(Method 1) The first method is to judge the relationship between a user and another user (parent-child relationship, boss / subordinate relationship) based on the conditions predetermined by the system, and when the relationship is recognized. This is a method of allowing the user (parent or boss) to save settings of another user (children or subordinates). In this method, when a user (parent or boss) requests that another user (children or subordinates) be set to save, the other user is not notified (the other user). Give permission for save settings (without asking). For this reason, it is particularly effective when the relationship between users is parent and child, especially when the child is a certain age or younger (for example, 13 years old or younger, the age group in which the parent does not want to save the history of information for adults). Is. Therefore, here, a case where the relationship between users is a parent and child and the child is 13 years old or younger will be described as an example.

First, the parent user logs in from the user terminal 110 with his / her own user ID and password, and accesses the page for saving setting application prepared in advance. Specify the user (child) you want to save and set on the save setting application page (enter the child's user ID, etc.) and send it to the server 130. Upon receiving the save setting request, the save setting process 164 checks the relationship between the user who made the save setting request and the designated user. Specifically, for example, referring to the user database of FIG. 20 described above, the addresses of both users are the same, and the age (determined from the date of birth) of the user (parent) is above a certain level (for example). It is determined whether the other user (child) is 13 years old or younger (determined from the date of birth). If the conditions are met (the relationship between the users is a parent and child and the child is 13 years old or younger), the child's user ID is registered in the save-settable user ID of the user (parent) in the user database. To do. After that, when the user (parent) logs in to the server 130 with his / her user ID and password, he / she can access the save setting page of the other user (child) and set the save setting of the child's search history. ..

The above condition is an example, and it may be determined that the child is a parent and child by matching the telephone number, the surname, the IP address, etc. in addition to the address or instead of the address. In addition, being a parent may be determined by the age difference with the child. Judging from the conditions illustrated here, it is not always the parents and children that meet the conditions, and there is a possibility that, for example, grandparents and grandchildren, relatives living together, siblings who are aged apart, and the like. That is, strictly speaking, it is determined whether the user is in a position to freely restrict the storage of the other user (children under 13 years old).

In addition, the server 130 (here, the user ID that can be set to save the user database) remembers that it is a parent and child in advance, and the parent can go to the save setting page of the child without applying for the above save setting. It may be accessible. Further, instead of registering the parent-child relationship in the database or the like, each time the parent desires the storage setting of the child's search history, the above-mentioned storage setting application and the determination of the parent-child relationship may be performed.

(Method 2) The second method is that when a user (parent or boss) requests a save setting application that specifies another user (child or subordinate), the other user (child or subordinate) is notified to that effect. Notify and ask for consent to the save settings by the user (parent or boss). If you agree, you can set the save settings thereafter. In this method, the user (parent or boss) is given permission to set the save setting, subject to the consent of the other user (children or subordinates). Therefore, it is effective when the relationship between users is a relationship between a boss and a subordinate, or when a child is a certain age or older (for example, 14 years or older) between a parent and child.

First, as in the above method 1, the user (parent or boss) inputs the user ID of another user (child or subordinate) on the save setting application page and sends it to the server 130. Upon receiving the save setting request, the save setting process 164 notifies the designated user (child or subordinate) that the user (parent or boss) desires the restriction. Specifically, for example, the notification is sent by sending an e-mail containing the URL to the page for consent to the e-mail address of the other user (children or subordinates) together with the text of the notification. Alternatively, the text of the notification and the URL link to the consent page may be displayed on the user-only page (Fig. 4 above) of the other user (children or subordinates).

When the other user (children or subordinates) accesses the consent page and gives consent (for example, clicks the "Agree" button displayed on the consent page), the user (parent or boss) in the user database ) Save Settable Register the user IDs of children and subordinates in the user IDs that can be set. After that, as in the above method 1, when the user (parent or boss) logs in to the server 130 with his / her user ID and password, he / she accesses the save setting page of the other user (children or subordinates). You can set the storage settings for children and subordinates.

In this second method, when the child was 13 years old or younger, the parent set the storage setting for the child by the above method 1, but the child was later not subject to the age limit (at 14 years old). It can also be used in the case of (becomes). In this case, for example, on the day the child turns 14, the child is notified of the consent page described above so that if the child consents, the parent can continue to set the child's storage settings.

<figref num="1">It is a figure which showed an example of the system configuration using the search history storage system of this embodiment.</figref><figref num="2">It is the figure which showed the main item of (a) search word database, (b) site history database, and (c) storage setting database, respectively.</figref><figref num="3">It is the figure which showed the main item of (a) label database and (b) evaluation item database, respectively.</figref><figref num="4">This is a configuration example of a user-only page transmitted to a user terminal in this embodiment.</figref><figref num="5">This is an example of a search result page on a search engine.</figref><figref num="6">It is a flowchart which showed an example of the flow of the search word saving process.</figref><figref num="7">It is a flowchart which showed an example of the flow of the site history saving process.</figref><figref num="8">This is an example of the site history list page.</figref><figref num="9">This is an example of a page for printing site history.</figref><figref num="10">This is an example of a search word list page.</figref><figref num="11">This is an example of a page for printing search words.</figref><figref num="12">This is an example of a site history edit page.</figref><figref num="13">This is an example of a label list page.</figref><figref num="14">This is an example of a label edit page.</figref><figref num="15">This is an example of the evaluation item list page.</figref><figref num="16">This is an example of the evaluation item edit page.</figref><figref num="17">This is an example of the search history setting page.</figref><figref num="18">This is an example of a prohibited word setting page.</figref><figref num="19">This is an example of a prohibited URL setting page.</figref><figref num="20">It is a figure which showed the main item of a user database.</figref>

Code description

110 User terminal 112 Browser 114 Cookie120 Internet 130 Server 140 Search system 142 Search database 144 Search processing 150 Search history storage system 151 Search word database 152 Site history database 153 Storage setting database 154 Label database 155 Evaluation item database 161 Search word storage Process 162 Site history save process 163 Search history transmission process 164 Save setting process 165 Label registration / update process 166 Evaluation item registration / update process 400 User-only page 410 Search box 411 Search text box 412 "Search" button 413 "Search history" Tab 420 Search history settings area 421 "Pause autosave" link 422 "Search history settings" link 430 Left navigation 440 Calendar display area 450 Recent search word display area 451 "More" link 460 Site list display area 461 Label order list 462 "More" link 463 Evaluation item order list 464 "More" link 470 Bookmark registration box 471 URL Text box for input 472 "Register" button 480 Main display area 500 Search result list page 510 Search result 511 Site name 512 Site overview 513 Site URL 520 Related category display area 530 Page navigation link 800 Site list 810 Navigation bar 811 "Check all Check box 812 "Delete" button 813 "Display list for printing" button 814 "Next 10" link 815 Display target selection link 816 Display number selection link 820 Site list display area 821 Date display field 822 Search word display field 823 Search type display field 824 Search count display field 825 "Research" link 830 Site history display field 831 Site name display field 832 Site overview display field 833 Site URL display field 834 Last visit date display field 835 Label display field 836 Evaluation display field 837 Comment display field 838 "More" link 900 Site history print page 901 Page title display field 902 Date display field 903 Search word display field 910 Site history display field 911 Site name display field 912 Site URL display field 913 Site outline display field 914 Last visit date display field 915 Label display field 916 Evaluation display field 917 Comment display field 1000 Search word list page 1010 Navigation bar 1020 Search condition list area 1030 Search condition display field 1031 Date display field 1032 Search word display field 1033 Search count display field 1034 Site history number display field 1035 Search type display field 1036 Search date display field 1100 Search word list print page 1101 Page title display field 1110 Search word list display field 1111 Search word display field 1112 Site history number display field 1113 Search type display field 1114 Search date and time display field 1200 Site history edit page 1210 "Delete this history" button 1220 Basic information edit input area 1221 Site name edit input field 1222 Site URL edit input field 1223 Site outline edit input field 1230 Arbitrary information edit input area 1240 Label edit input area 1241 Label input field 1242 New label registration field 1243 Label list display field 1250 Evaluation edit input area 1251 Evaluation Input field 1252 New evaluation item registration field 1253 Evaluation list display field 1260 Comment edit input field 1270 "Save" button 1300 Label list page 1310 New label registration area 1311 New label input text box 1312 "Add" button 1320 Navigation bar 1321 "Check all" check Box 1322 "Delete" button 1323 Display order selection link 1330 Label list area 1331 Label name display field 1332 Site history number display field 1333 "Edit" link 1400 Label edit page 1410 Before change Label display field 1420 After change Label input field 1430 "Save" Button 1440 "Delete" button 1500 Evaluation item list page 1510 New evaluation item registration area 1511 New evaluation item input text box 1512 "Add" button 1520 Navigation bar 1521 "Check all" check box 1522 "Delete" button 1523 Select display order Link 1530 Evaluation item list area 1531 Evaluation item name display field 1532 Site history number display field 1533 "Edit" link 1600 Evaluation item edit page 1610 Evaluation item display field before change 1620 Evaluation item input field after change 1630 "Save" button 1640 "Delete" button 1700 Search history setting page 1710 Save limit setting area 1711 Detailed setting field 1712 Number of items displayed per page Setting field 1713 Filtering setting field 1714 "Save settings" button 1720 Bookmark import area 1721 Path input field 1722 "Browse" button 1723 "Import" Button 1800 Prohibition word setting page 1810 Prohibition word input field 1820 Prohibition word deletion field 1830 Prohibition word list 1900 Prohibition URL setting page 1910 Prohibition URL input field 1920 Prohibition URL deletion field 1930 Prohibition URL list