JP4976044B2 - Search history storage system - Google Patents

Description

  The present invention relates to a system in which a user saves a search history using a search engine in a server and makes the user use it.

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 moving image file, etc.) is found, for example, Google, Yahoo, Google In many cases, keyword search (search by inputting a search word) is performed using a search engine provided on a homepage such as, Infoseek or the like.
Normally, a search engine search database stores a title (name), URL, summary (for example, a part of sentences in an automatically collected HTML file), etc. as site information collected from the Internet. In the list of search results that the user browses with the browser, these titles and URLs (there are links to the sites), outlines, and the like are displayed. The user can easily access (visit) the site by simply clicking the link to the desired site from the list.

  In order to collect and save the necessary and favorite sites among the sites visited in this way, a bookmark (favorite) registration function prepared in the browser is usually used. This allows a shortcut file to a site to be saved locally on a personal computer with a simple operation, and thereafter, access can be made from a list of saved bookmarks (favorites).

However, in the current search engine, in many cases, the number of search results is enormous. Therefore, it is not practical to bookmark all visited sites (including those that are necessary only temporarily) because it takes time and is difficult to browse later.
On the other hand, if you do not leave a browsing history, if you want to return to the site you visited before, you must search again with the search engine, and the search database is updated from time to time, so as before You can't always find the site.

  To solve this problem, for example, in “personalized search” of Google (Non-patent Document 1), when a search engine is used while a registered user is logged in, a search condition (search word) entered by the user and a search It provides a service that automatically saves the information of the visited sites from the list of results and allows users to view their search history in a browser.

http://www.google.com/

The conventional search history storage service automatically saves all search histories. For this reason, information that the user does not want to collect (for example, information for adults or information that includes words that the user does not want) is also stored as a history. Therefore, the unnecessary history must be manually deleted later on the browser by the user.
In addition, if the search history is stored on the server, the user can share the search history with other users (for example, share his search history with other users or view other users' search history). Can be provided. In this case, in particular, there is a high need for a system that does not collect unnecessary search histories.

In order to solve the above problem, the present invention provides a search history storage system in which a user terminal stores a search history using a search engine in a server, and stores a search history storage restriction condition A setting storage means, and a search word storage means for storing the search word as a search history in the history storage means when the search word search word is received from the searcher's terminal, according to the stored restriction condition; When receiving from the terminal of the searcher that the search result site corresponding to the search word is accessed, the access information to the site is associated with the search word according to the stored restriction condition In response to a request from the searcher's terminal, the search history of the searcher is stored in the history storage means that stores the search history as the search history above. Read from gravel storage means, and search history transmission means for transmitting the search word are associated with each other in the search history read, and a list page that displays access information to the site to the terminal, the searcher's terminal When receiving the evaluation information indicating the evaluation to one site indicated by the access information of the search history, the search word, the access information to the one site associated with the search word, and the Evaluation registration means for setting the evaluation information in the corresponding search history in the history storage means for associating the evaluation information with each other, and the search history transmission means mutually in the search history read from the history storage means The list page displaying the search word, the access information to the site, and the evaluation to the site that are associated with each other And it transmits the search's terminal, a search history storage system, characterized in that.
Further, the search history transmission means further reads the search history of the searcher in response to a request from a terminal of a viewer different from the searcher, and displays the list page based on the read search history. It is good also as a characteristic to transmit to the terminal of.
Further, the storage restriction condition of the storage setting storage unit includes a prohibited word, the search word storage unit does not store the search condition including the prohibited word, and the site history storage unit includes a site including the prohibited word. The information may not be stored.
The storage restriction condition of the storage setting storage unit may include a prohibited URL, and the site history storage unit may not store site information including the prohibited URL.
In addition, an edit page for editing the search history is transmitted to the searcher's terminal, and the search history transmission means receives the edit content set in the edit page from the searcher's terminal. The relevant item of the search history in the history storage means may be updated with the edited content.
In addition, a storage setting unit for storing the storage restriction condition in the storage setting storage unit is further provided, and a storage setting page for setting the storage restriction condition of the searcher is transmitted to the searcher's terminal. The storage setting unit receives the storage restriction condition set in the storage setting page from the searcher's terminal, and stores the received storage restriction condition in the storage setting storage unit. It is good.
Further, the storage setting means further transmits a storage setting application page for causing the terminal of an applicant different from the searcher to specify the searcher to which the setting of the storage restriction condition is applied, When it is determined whether the applicant and the searcher specified on the storage setting application page have a predetermined relationship, and the applicant and the specified searcher have the predetermined relationship The storage setting page for setting the storage restriction condition of the designated searcher is transmitted to the applicant's terminal, and the storage restriction condition set in the storage setting page is stored in the storage It may be stored in the setting storage means.
The present invention also provides a search history storage system in which a user terminal stores a search history using a search engine in a server, a storage setting storage means for storing search history storage restriction conditions, and a searcher A search word storage means for storing the search word in the history storage means as a search history in accordance with the stored restriction condition, from the searcher terminal, When it is received that the search result site corresponding to the search word is accessed, the history is set as a search history after associating the access information to the site with the search word in accordance with the stored restriction condition. In response to a request from the searcher's terminal, the search history of the searcher is read from the history storage means in response to a request from the searcher's terminal. Search history transmission means for transmitting the search word associated with each other in the retrieved search history and a list page displaying the access information to the site to the terminal; Storage setting means for storing in the search means, a save setting page for setting the search restriction condition of the searcher is transmitted to the searcher's terminal, and the save setting means is used for the save setting The storage restriction condition set in the page is received from the searcher's terminal, the received storage restriction condition is stored in the storage setting storage means, and the storage setting means is further different from the searcher Send the storage setting application page to the applicant's terminal to specify the searcher to which the setting of the storage restriction condition is applied, and the applicant and the storage setting application Whether or not the searcher specified in the page is in a predetermined relationship, and when the applicant and the specified searcher are in the predetermined relationship, Transmitting the storage setting page for setting the storage restriction condition to the applicant's terminal, and storing the storage restriction condition set in the storage setting page in the storage setting storage unit; Is a search history storage system characterized by
A program for causing a computer to function each means of the search history storage system described above is also the present invention.

According to the search history storage system of the present invention, the search history (in this embodiment, the search condition and the history of the site accessed (visited) from the search result) is automatically stored. At that time, the user can freely specify prohibited words, prohibited URLs, etc. to impose storage restrictions, so that unnecessary information or information that does not need to be saved should not be collected easily and meticulously. Can do. Note that the content of the storage restriction can be freely determined by the system according to necessity.
In addition, the collected search history can be used effectively, such as when the user adds information (for example, comments, evaluations, etc.) to the search history, or sorts and organizes by label. The contents such as information to be added to the search history can be freely determined by the system according to necessity.
In addition, since the search history is stored in the server, the system can easily share the search history with other users. The ability to perform the above storage restriction and editing is particularly useful when sharing a search history.

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 overview 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, setting of storage restriction will be described (FIGS. 17 to 19).
(4) Next, storage of the search history will be described (FIGS. 5 to 7).
(5) Finally, transmission of a search history list page or the like to the user terminal and editing of the search history by the user will be described (FIGS. 8 to 16).

(1. System overview)
First, an overview of the system of this embodiment will be described with reference to the system configuration diagram and database items in FIGS.
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, a user terminal 110 is a terminal such as a personal computer used by a user, and connects to a server 130 through the Internet 120.
The browser 112 is conventional normal browser software installed in 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. Note that 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. The cookie 114 is transmitted from the server 130 and stored in the user terminal 110 when the user terminal 110 first accesses a search engine top page or the like, for example. Thereafter, 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. Thereby, even if a user does not perform so-called user registration and login, the server 130 can identify the user (user terminal 110). Instead of the above cookie, user registration may be performed 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 is a system that provides the user with a conventional normal search engine (for example, a search engine provided on a top page such as Google, Yahoo, Google, Infoseek, etc.).
The search database 142 is the above-described conventional search database, and stores site information (name (title), URL, outline, etc.) collected on the Internet.
Furthermore, in the present embodiment, these sites are stored with types (for example, web pages, image files, video files, blogs (top page), news articles (web pages), etc.). The user can search by inputting a search word for all types, and can search by selecting a type of search target and inputting the search word. Such a search engine is a prior art.
In the search process 144, when the user inputs a search condition on the search page displayed on the browser 112 of the user terminal 110 and performs a search, the search database 142 is searched, and the name, URL, This is a program for performing processing for transmitting a page displaying a summary or the like to the user terminal 110.

(1-3. Search history storage system)
The search history storage system 150 is a search history storage system according to the present embodiment, and stores a history of searches performed by a user using a search engine. In the present embodiment, the search condition and the history of the site accessed (visited) from the search result are stored as the search history. When storing the search history, whether or not the search history can be stored is determined according to the storage restriction condition set by the user.
Also, the user can browse the search history so that the user can delete / 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 input by the user. The search word database 151 is stored in the search word storage process 161. The processing procedure of the search word storage process 161 will be described in detail later.
FIG. 2A is a diagram showing an example of main items of the search word database 151. “User ID” is an ID for uniquely identifying a user. As described above, in this embodiment, information stored in the cookie 114 is used. “Search No.” is a number uniquely assigned to the search of the user. “Search word” is the input search word. “Search type” is a selected type (for example, the above-described web page, image, video, blog, news, etc.).
In addition, the user can repeatedly perform a search again from the search history under the same search condition. “Number of searches” is the number of times the user has performed the search. “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 by a site history storage process 162. The processing procedure of the site history storage process 162 will be described in detail later.
FIG. 2B is a diagram showing an example of main items in the site history database 152. The “user ID” is the above-described user ID (information stored in the cookie 114 in the present embodiment). “Search No.” is information indicating which search result the site has been viewed from. It corresponds to.
“Site URL”, “Site Name”, and “Site Summary” are the site name (title), URL, and summary stored in the search database 142, respectively.
Further, the user can repeatedly visit the same site from the search history. “Number of times of access” is the number of times the user visited the site. “Last visit date” is the date and time when the user last visited the site.

The “comment”, “evaluation item ID”, “evaluation”, and “label ID” are items that allow the user to add information later to the site history stored in the site history database 152.
The comment is a user comment on the site.
The label is a label for classifying the site, such as “news” or “recommended”.
In the present embodiment, it is assumed that 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 / editing of labels will be described in detail later.
An example of main items in the label database 154 is shown in FIG. “User ID” is the above-described user ID (information stored in Cookie 114). “Label ID” is an ID uniquely assigned to a label. The “label name” is a label name such as “news” or “recommended”.

The evaluation is an evaluation of the user to the site, and includes evaluation items (for example, “interesting”, “cheap”, etc.) and evaluations (for example, five-step evaluation) on these evaluation items.
In this embodiment, it is assumed that 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 / editing of evaluation items will be described in detail later.
An example of main items in the evaluation item database 155 is shown in FIG. “User ID” is the above-described user ID (information stored in Cookie 114). “Evaluation item ID” is an ID uniquely assigned to an evaluation item. “Evaluation item name” is an evaluation item name such as “interesting” or “cheap”.
Note that the above-described functions for attaching comments, labels, and evaluations are not essential functions in the present embodiment, but comments and evaluations are particularly useful when the search history is disclosed to other users. Labels are useful for organizing many 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 search histories of the user in response to a request from the user and transmitting the web page to the user terminal 110. The user can browse the search history with 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. Note that 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 contents such as storage restrictions. The save setting process 164 is a process for registering / updating the setting by the user in the save setting database 153.
FIG. 2C is a diagram showing an example of main items of the storage setting database 153. “User ID” is the above-described user ID (information stored in Cookie 114). The “save enable / disable flag” is a flag indicating whether or not to save the search history. The “saving pause flag” is a flag indicating whether or not saving is paused.
“Storage restriction information (prohibited word)” is a keyword designated by the user as a prohibited word (information including this word is not stored as a search history). In this embodiment, it is assumed that a plurality of prohibited words can be designated.
“Save restriction information (prohibited URL)” is a URL (or a part of the URL) designated by the user as a prohibited URL (information including this URL is not saved as a search history). In this embodiment, it is assumed that a plurality of prohibited URLs can be specified.
The “storage restriction information (adult genre storability flag)” is information that the search engine provider determines to be an adult genre (for example, information including keywords or URLs for adults designated by the search engine provider) This flag indicates whether to save as a search history.

"History capture flag" is a flag that indicates whether or not the history of searches performed by registered users in the logoff state when the search engine provider has registered users will be taken over when logging on thereafter. is there.
“Number of display items per page” is an item indicating how many histories are displayed per page in the search history list displayed on the browser 112 of the user terminal 110.

  Note that the server 130 may not be a single server. 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 program in each system may be stored separately in another server.

(2. Configuration of user-specific pages)
Next, referring to FIG. 4, a user-specific web page (hereinafter referred to as a user-specific page) for a user to perform a search and use the search history (browsing / deleting / editing the search history and setting a storage limit) Will be explained. As described above, the search history transmission processing 163 performs creation of each page of the search history and transmission to the user terminal 110.
FIG. 4 is an example of a user-dedicated page of this embodiment. As described above, the server 130 identifies the user terminal by the cookie 114 transmitted from the browser 112 when accessing from the user terminal 110. Accordingly, the search history of the user can be read from each database and displayed on the user-dedicated page.

In the user-only page 400, a search box 410 is an area where the user searches.
Clicking on the “Search History” tab 413 on the far right of the tabs lined up at the top of the search box 410 displays a list of all of the user's search history (search conditions and site history corresponding to the search). Transition to the site history list page (displayed in the main display area 480 in the present embodiment, and so on). The site history list page will be described later with reference to the example of the site history list page of FIG.
Here, when the user inputs 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 displaying the search results as a list. Transition to.
In the example of FIG. 4, a “search history” tab 413 is provided, but instead of the “search history” tab 413, a page displayed by clicking each tab (for example, an “image” tab is displayed). You may make it paste the link for changing to the page of a user's search history on the page displayed by clicking. That is, the display is not limited to the display of the “search history” tab 413, and text for prompting a transition to the search history page (text with a URL pasted) may be displayed on each site.

  The other tabs at the top of the search box 410 (in the example of FIG. 4, Google search, Infosearch search, directory, blog, image, video, software, news) correspond to the types of the search database 142. When the user clicks a desired tab and inputs a keyword in the search text box 411 and performs a search, the search processing 144 is performed using the selected type and the input keyword (search word) as a search condition. 142 is searched, and the search result transits to a page displaying a list. 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 that displays a link to a page or the like on which the user sets storage restrictions.
The “pause automatic saving” link 421 is a link that temporarily stops saving the search history. Specifically, when the user clicks the “pause automatic save” link 421, the save pause flag in the save setting database 153 is turned on (cannot be saved), and the subsequent search history is not saved.
When automatic saving is paused, the display of the “pause automatic saving” link 421 changes to “resume automatic saving”. When the user clicks the “Resume automatic saving” link, the storage suspension flag in the storage setting database 153 is turned off (save is possible), and the subsequent search history is stored.
The “search history setting” link 422 is a link that transitions to a page on 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.

The left navigation 430 is a part that displays the recent search history of the user together with a link to a list display page. The left navigation 430 includes a calendar display area 440, a recently searched word display area 450, a site list display area 460, and a bookmark registration box 470.
In the calendar display area 440, the search history is displayed in a calendar format. The date of the calendar is made to correspond to the last search date / time of the search word database 151. Also, the number of site histories for that day is displayed in different colors, making it easier for the user to see.
When the user clicks on a date link, the screen transitions to a site history list page displaying a list of search history for that day (search conditions and site history corresponding to the search).

In the recent search word display area 450, user searches are displayed in order from the latest (in this example, four cases are displayed). Here, “Cookie-5 times (8)” is displayed from the left: search word, number of searches (total number of searches in all types by the search word), number of site histories visited from the search (same search) Total number of site histories of all types by word).
Clicking a search word takes you to the site history list page that lists the corresponding site history.
When a “More” link 451 is clicked, a transition is made to a search word list page displaying a list of 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 order of frequently used labels (label order list 461) and order of frequently used evaluation items (list of order of evaluation items 463). ing.
When the “site list” link is clicked, a transition is made to a site history list page displaying a list of all the user search histories (search conditions and site histories corresponding to the search).
When each label name displayed in the label list display unit 461 is clicked, a transition is made to a site history list page displaying a list of site histories with the corresponding label. Also, when a “view more” link 462 is clicked, a transition is made to a label editing page displaying a label list. The label edit page will be described in detail later with reference to FIG.
When each evaluation item name displayed in the evaluation item list display unit 463 is clicked, a transition is made to a site history list page displaying a list of site histories with the corresponding evaluation. Clicking on “View more” 464 transitions to an evaluation item edit page displaying a list of evaluation items. The evaluation item edit page will be described in detail later with reference to FIG.

The bookmark registration box 470 is an input box in which the user can register a site by himself / herself. When a desired URL is entered in the URL input text box 471 and the “Register” button 472 is clicked, the URL is registered in the site history database 152. At this time, a label “bookmark” prepared in advance by the system is attached.
Editing of the registered site (addition of site name, comment / evaluation, etc.) is performed on the site history editing page as in the normal site history. The site history editing page will be described in detail later with reference to the example of the site history editing page in FIG.

(3. Setting storage restrictions)
Next, the setting of the storage restriction by the user will be described with reference to each page of FIGS.
As described above, when the “search history setting” link 422 is clicked in FIG. 4, a transition is made to a search history setting page in which the user sets storage restrictions.
An example of the search history setting page is shown in FIG. The user sets the search history storage method, the number of display items, and the like in each column of “search history setting” 1710, and the setting contents are stored in the storage setting database 153.

In the detailed setting column 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. When a check box is clicked and a “save setting” button 1714 is clicked, the save enable / disable flag in the save setting database 153 is updated to “save possible”, and the subsequent search history is saved. If the check is removed and the “save setting” button 1714 is clicked, the save enable / disable flag is updated to “save not possible” and the subsequent search history is not saved.
In addition, “capture the previous search history at the time of login” is a search saved when the registered user is not logged in when the provider of the search history storage system of the present embodiment is also performing user registration. This is a check box for setting whether to take over the history after login. The setting is stored in the history fetch flag of the saved setting database 153.

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

The filtering setting column 1713 is a column for setting the storage limit in detail. If the “Do not save search words and browsing sites that contain specified words” checkbox is checked, the search history that contains the registered words will not be saved.
In the present embodiment, for example, it is assumed that prohibited words (prohibited words) and prohibited URLs (prohibited URLs) can be registered. When a “prohibited word / URL setting” link is clicked, a transition is made to a prohibited word setting page shown in FIG. 18 and a prohibited URL setting page shown in FIG.
To register a prohibited word, in the prohibited word setting page of FIG. 18, enter the prohibited word in the text box of the prohibited word input field 1810 and click the “Register” button. The registered prohibited word is stored in the storage restriction information (prohibited word) of the storage setting database 153. In the prohibited word list 1830, prohibited words that have already been registered are displayed. 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 are checked.
In order to register a prohibited URL, the prohibited URL is entered in the text box of the prohibited URL input field 1910 on the prohibited URL setting page in FIG. 19 and the “Register” button is clicked. The registered prohibited URL is stored in the storage restriction information (prohibited URL) of the storage setting database 153. The prohibited URL list 1930 displays prohibited URLs that have already been registered. The prohibited URL is deleted by checking the check box on the left side of the prohibited URL list 1930 and clicking the “delete” button in the prohibited URL deletion column 1920. Here, when “check all” is clicked, all prohibited URLs are checked.

Returning to the search history setting page 1700 of FIG. 17, the bookmark import area 1720 is an area where a user can add a bookmark registered by the function of the browser 112 to the site history of the present embodiment with a simple operation.
To import a bookmark, enter the path to the bookmark file in the path input field 1721 and click the “Import” button 1723, the bookmark information (URL, site name, etc.) is registered in the site history database 152. In the present embodiment, a label “bookmark” prepared in advance by the system is attached. When a “Browse” button 1722 is clicked, a file selection dialog box is displayed, and the path to the bookmark file can be easily specified.

(4. Save search history)
Next, search history storage will be described with reference to the search result page of FIG. 5 and the flowcharts of FIGS. Note that the search history is stored according to the storage limit set by the user in (3. Setting of storage limit) described above.

(4-1. Saving search conditions)
As described above, when the user performs a search using the search system 140 on the user dedicated page 400 of FIG. 4, the search processing 144 searches the search database 142 and displays the search result list page (FIG. 5) as the user terminal. At this time, the search word storage processing 161 stores a keyword (search word) or the like input as a search condition in the search word database 151.

FIG. 5 shows a search result when the user selects the type “Google search” on the tab at the top of the search box 410 and enters the keyword (search word) “Hattori-kun” in the search text box 411 to perform a search. It 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-specific page 400 in FIG. 4 described above.
In the search result list page 500, information such as a site name 511, a site outline 512, and a site URL 513 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. When the search result page is to be changed to another page, the number of pages displayed on the page moving link 530 is clicked. These are functions of a conventional search engine.

FIG. 6 is a flowchart showing an exemplary flow of the search word storage process 161.
When a user performs a search using a search engine and receives a search condition input from the user terminal 110 (S610), it is first determined whether the user is a user who can store a search history (S620). Specifically, the storage permission / inhibition flag and the storage suspension flag in the storage setting database 153 corresponding to the user ID (Cookie) of the user are referred to.
If either or both of the storage permission flag and the storage suspension flag are “storing is impossible” (No in S620), do nothing (do not register the search in the search word database 151). Exit.
On the other hand, if both the storage permission flag and the storage suspension flag are “saveable” (Yes in S620), it is determined whether the search condition (search word) is subject to storage restriction (S630). ). Since the search condition in this embodiment is search word + type, it is determined whether the search word is subject to storage restriction. That is, it is determined whether or not the search word corresponds to the storage restriction information (prohibited word) with reference to the storage setting database 153 corresponding to the user ID (Cookie) of the user.
Further, when the storage restriction information (adult genre storage enable / disable flag) in the storage setting database 153 cannot be stored, it is determined whether or not the search word corresponds to an adult genre determined by the search engine provider in advance.

If it is determined that the search word is subject to storage restriction (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 restriction (No in S630), the search condition is registered in the search word database 151, and the process ends (S640). Specifically, in this embodiment, each item of the search word database 151, that is, the user ID, the search number, the search word, the search type, the number of searches, and the last search date and time are stored.
In the example shown in FIG. 5 described above, “hattori-kun” is stored as the search word, and “Web search” is stored as the search type. Further, “1” is stored as the number of searches, and the current search date is stored as the last search date. For example, if “Hattori-kun” is a storage restriction target, it is not stored in the search word database 151.

(4-2. Saving site history)
When the user visits a site from the search result list (when the user clicks the name 511 or URL 513 of the site that the user wants to see in the search result list of FIG. 5), the user jumps to the site and saves the site history. 162 stores 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 storage process 162.
When the fact that the link to the site has been clicked is received from the search result list page (FIG. 5 described above) (S710), it is first determined whether or not the user can save the search history (S720). In the present embodiment, specifically, similarly to the search word storage processing 161 described above with reference to FIG. 6, the storage permission / inhibition flag and the storage suspension flag in the storage setting database 153 corresponding to the user ID of the user. If the data cannot be stored (No in S720), the process ends without doing anything (without registering the site in the site history database 152).
On the other hand, if storage is possible (Yes in S720), it is determined whether the site is subject to storage restriction (S730). Specifically, in this embodiment, referring to the storage setting database 153 corresponding to the user ID of the user, information on the site (site name, URL, site outline, etc. registered in the search database 142) It is determined whether the storage restriction information (prohibited word) and the storage restriction information (prohibited URL) are included in the information.

Further, similarly to the search word storage processing 161 described above with reference to FIG. 6, when the storage restriction information (adult genre storage permission flag) cannot be stored, the site is determined in advance by the search engine provider side. Judge whether it corresponds to a certain adult genre.
If it is determined that the site is subject to storage restriction (Yes in S730), nothing is done (the site is not registered in the site history database 152), and the process is terminated.
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, the search number (corresponding to the search number in the search word database 151), and the site URL of the site history database 152 described above with reference to FIG. , Site name, site outline, number of accesses (input 1 as an initial value), last visit date (current visit date) is stored.

(5. Search history transmission and editing by the user)
Finally, transmission of a search history list page or the like to the user terminal and editing of the search history by the user will be described with reference to each page shown in FIGS. The search history transmission process 163 performs the process of transmitting each page to the user terminal 110 and storing the edits by the user in the database.

(5-1. Transmission of site history list)
As described above, in the user-specific page 400 of FIG. 4, the user searches the search history in the search box 410, clicks the date on the calendar display unit 430, clicks the “site list” link 460, and labels When the “view more” link 462 in 461 is clicked, the “view more” link 464 in the evaluation item order list 463 is clicked, etc., a transition is made to a site history page displaying a list of target search histories.

FIG. 8 is an example of a site history list page. FIG. 8 is an example when a list of search histories to be displayed is displayed for each search condition. The display items, display order, etc. are examples.
In the site history list page 800, the site list display area 820 displays the search history (search conditions and site history corresponding to the search) to be displayed in order from the latest search date of the search word database 151. Yes.
In the date display column 821 and the search word display column 822, the last search date and the search word of the search word database 151 are displayed, respectively. When a search word is clicked, a transition is made to a site history list page displaying all site histories (including site histories that are not to be displayed) corresponding to the 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. The search count display field 824 displays the search count of the search word database 151.
When the “re-search” link 825 is clicked, the search process 144 searches the search database 142 again under the same search conditions, and transitions to the search result page (FIG. 5). At the same time, the search history transmission processing 163 updates the last search date / time of the search word database 151 and increases the number of searches by one.

The site history display column 830 displays the site history to be displayed, for example, in ascending order of site names.
The site name display field 831, the site outline display field 832 and the site URL display field 833 display the site name, site outline, and site URL of the site history database 152, respectively. The last visit date etc. display field 834 displays the last visit date and time and the number of accesses of the site history database 152.
Here, when a site name or a site URL is clicked, a transition is made to that site, the last visit date and time of the site history database 152 is updated, and the number of accesses is increased by one. If “edit” on the right side of the site name 831 is clicked, a transition is made to a page for editing the site history (site edit page in FIG. 12). The editing of the site history will be described 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. When a label name is clicked, a transition is made to a site history list page displaying a list of site histories with the 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. When an evaluation item name is clicked, a transition is made to a site history list page displaying a list of site histories assigned with the evaluation item.
Comments in the site history database 152 are displayed in the comment display field 837. The comment is displayed up to a predetermined number of characters, for example, and the entire text is displayed when the “More” link 838 is clicked.

In addition, when a “check all” check box 811 is clicked in the navigation bar 810, check boxes for all site histories displayed on the current page are checked. The “delete” button 812 is a button for deleting the checked site history from the site history database 152.
The number-of-sites display column 814 indicates the number of site histories to be displayed and what number is currently displayed. Further, the “next 10 cases” link 814 is a link that transits to the next page of the site list. From the second page onward, the “Previous 10” link may also be displayed. The number of items to be displayed on one page depends on the number of items to be displayed on one page of the storage setting database 153.
The display target selection link 815 is a link for selecting a 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 to be displayed on one page.

A “display list for printing” button 813 is a button for transitioning to a page displaying a list of the site history selected by the check box for printing. For example, another window may be activated and displayed instead of the page transition.
An example of the site history printing page is shown in FIG. In the site history printing page 900, the page title display column 901 displays the title of the printing page (“site list” in the example of FIG. 9). Further, it is preferable to display necessary information in a date display column 902, a search word display column 903, etc. in an easy-to-see manner. In the site history display column 910, for example, for each site history, the site name is displayed in the site name display column 911, the site URL is displayed in the site URL display column 912, the site overview is displayed in the site summary display column 913, and the last visit date. The display date and time of the last visit in the equal display column 914, the label name in the label display column 915, the evaluation item and evaluation in the evaluation display column 916, and the comment in the comment display column 917 may be displayed in an easy-to-read form such as a table. .

(5-2. Transmission of search condition list)
Further, in FIG. 4 described above, when the user clicks “More” 451 of the recent search word 450, the screen shifts 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 with reference to FIG. 8, and the selected search condition is deleted, the display target is selected, and the number of display items is set. This is an area for displaying a print page of the selected search condition.
FIG. 11 shows an example of a search word printing page. The page title display field 1101 displays the title of the page for printing (“searched word list” in the example of FIG. 11). In the search word list display column 1110, for example, the search word display column 1111 indicates the search word, and the site history number display column 1112 indicates the number of site histories corresponding to the search (same search number). The search type display field 1113 displays the search type, and the search date / time display field 1114 displays the last search date / time in a tabular format.

Returning to the search word list page 1000 of FIG. 10, the search condition list area 1020 is an area for displaying a list of search conditions. In the date display field 1031 and the search word display field 1032 of the search condition display field 1030, the last search date and the search word of the search word database 151 are displayed, respectively. When a search word is clicked, a transition is made to a site history list page displaying a list of site histories corresponding to the search.
The search count display column 1033 displays the search count of the search word database 151. The site history number display column 1034 displays the number of site histories corresponding to the search. The search type display column 1035 and the search date display column 1036 display the search type and the last search date of the search word database 151, respectively.

(5-3. Editing site history)
When the user clicks “edit” on the right side of the site name display field 831 in the site history list page of FIG. 8 described above, the screen transitions to the site history edit page of FIG.
When the “delete this history” button 1210 is clicked on the site history editing page 1200, this site history is deleted from the site history database 152.
The basic information editing input area 1220 is an area for editing basic information (site name, site URL, site outline) of the site history.
In the site name edit input field 1221, the site name of the site history database 152 is displayed and can be edited by the user. In the site URL edit input field 1222, the site URL of the site history database 152 is displayed and can be edited by the user. Note that the title and URL are indispensable items of the site history and cannot be left unentered.
In the text box of the site summary edit input field, the site summary of the site history database 152 is displayed and can be edited by the user.
When the basic information is edited and the “save” button 1270 is clicked, the site history database 152 is updated with the input contents.

The arbitrary information edit input area 1230 is an area for adding and editing arbitrary information of the site history (in this embodiment, label / evaluation / comment).
The label is set in the label edit input area 1240. Since the label registered in the label database 154 is displayed in the list box in the label input field 1241, the label to be attached is selected. When a label is attached, a label ID is added to the site history database 152.
If a new label (not yet registered in the label database 154) is to be added, a new label name is entered in the text box of the new label registration field 1242, and the "Add" button is clicked. A label is registered at 154 and the label ID of the label is added to the site history database 152.
A label list display field 1243 displays a list of labels attached to the site history. When the “x” button on the left side of each label in the label list display field 1243 is clicked, the label is removed from the site history (the label ID of the site history database 152 is deleted).

Also, new addition and editing 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 processing 165.
In FIG. 4, when “More” 462 is clicked, a transition is made to the label list page of FIG. If a new label is to be created, a label name is entered in the new label input text box 1311 in the new label registration area 1310 and an “add” button 1312 is clicked.
The label list area 1330 displays a list of labels registered in the label database 154. In the label name display field 1331, the label name of the label database 154 is displayed. When a label name is clicked, a transition is made to a site history list page displaying a list of site history (site history having the label ID of the label) with the label. The site history number display column 1332 displays the number of site histories to which the label is attached. The display order selection link 1323 is a link that specifies whether to display the label list 1330 in order of the number of site history records or in order of label names.

To delete a label, check the check box on the left side of each label name in the label list and click a “delete” button 1322. Clicking “Check All” 1321 selects all the labels in the label list.
The label editing is performed on the label editing page of FIG. 14 which transitions when an “edit” link 1333 on the right side of each label name in the label list is clicked. In the label edit page 1400, the current label name is displayed in the label display field 1410 before change. When it is desired to change the label name, the changed label name is input to the changed label input field 1420 and the “Save” button 1430 is clicked. Clicking on the “Delete” button 1440 deletes the label from the label database 154.

Returning to the site history editing page 1200 of FIG. 12, the evaluation items are set in the evaluation editing input area 1250. Since the evaluation items registered in the evaluation item database 155 are displayed in the list box in the evaluation input field 1251, the evaluation item to be added is selected, and the evaluation (e.g., 5 levels from 1 to 5) is selected from the evaluation selection list box. ) Is selected. Then, the evaluation item ID and the evaluation are added to the site history database 152.
If you want to give 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 evaluation of the evaluation item are added to the site history database 152.
In the evaluation list display field 1253, evaluation evaluation items attached to the site history are listed. When the “x” button on the left side of each evaluation item in the evaluation list display field 1253 is clicked, the evaluation is removed from the site history (the evaluation item ID and evaluation in the site history database 152 are deleted).

Further, new addition and editing of evaluation items are performed on the evaluation item list page of FIG. 15 and the evaluation item edit 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.
In FIG. 4, when “More” 464 is clicked, a transition is made to the evaluation item list page of FIG. If a new evaluation item is to be created, an evaluation item name is entered in the new evaluation item input text box 1511 in the new evaluation item registration area 1510 and an “add” button 1512 is clicked.
The evaluation item list area 1530 displays a list of evaluation items registered in the evaluation item database 155. In the evaluation item name display field 1531, the evaluation item name of the evaluation item database 155 is displayed. When an evaluation item name is clicked, a transition is made to a site history list page displaying a list of site histories (the site history having the evaluation item ID of the evaluation item) attached with the evaluation item. The site history number display column 1532 displays the number of site histories to which the evaluation item is attached. 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 history records or in the order of evaluation item names.

To delete an evaluation item, a check box on the left side of each evaluation item name in the evaluation item list is checked, and a “delete” button 1522 is clicked. If “Check All” 1521 is clicked, all evaluation items in the evaluation item list can be selected.
The evaluation item is edited on the evaluation item editing page of FIG. 16 which is transitioned by clicking the “edit” link 1533 on the right side of each evaluation item name in the evaluation item list. In the evaluation item edit page 1600, the current evaluation item name is displayed in the evaluation item display field 1610 before change. When it is desired to change the evaluation item name, the changed evaluation item name is input to the post-change evaluation item display field 1620 and the “Save” button 1630 is clicked. When a “delete” button 1640 is clicked, the evaluation item is deleted from the evaluation item database 155.

Returning to the site history edit page 1200 of FIG. 12, a comment edit input field 1260 is a text box for inputting and editing a comment.
When these arbitrary information is input and the “save” button 1270 is clicked, the site history database 152 is updated with the input contents.
Although the above-mentioned arbitrary information of the site history is not essential to the present embodiment, the comment and the evaluation are particularly useful when the search history is disclosed to other users (and also viewed by other users). Labels are useful for organizing many 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 to be browsed / edited has been described as an example. However, the search history of other users may be browsed. Thereby, a user can share a search history.
In this case, the user performs user registration in advance with the server 130, logs in with a user ID and password, and uses the search system 140 and the search history storage system 150 of this embodiment. The search history is stored corresponding to the user ID.
As a result, the search history of other users is transmitted, for example, in response to a request from the user, or automatically determined by the system and transmitted (for example, the evaluation / comments of other users for the same search history are transmitted). (E.g., sending a search history of a user who has a common point in age, registered profile, etc.).

In the above description, the case where the user performs the save setting only for his / her search history has been described. For example, there are cases where the parent wants to limit the storage for the child search, or the supervisor wants to limit the storage for the subordinate search. It is 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.), the user (parent A search history storage system capable of setting the storage of other users (children or subordinates) by application from a supervisor will be described.
In the second embodiment, the user needs to be registered in the server 130 as in the case of the search history sharing described above. Therefore, a user database in which users are registered is prepared in the server 130 in the system configuration diagram of FIG. Here, each process of the second embodiment will be described as being implemented in the storage setting process 164 described above.

FIG. 20 shows 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 this embodiment. The user inputs these user ID and password, logs in to the server 130, and uses the search system 140 and the search history storage system 150 of this embodiment.
“Name”, “Birth date”, “Address”, and “Telephone number” are the user's name, date of birth, address, and phone number, respectively. Furthermore, profiles such as hobbies and preferences may be registered in the user database. “Mail address” is the user's email address.
The “settable user ID” is a user ID of another user (for example, a child or a subordinate) that can be set by the user (for example, a parent or a superior). Note that the association between the parent or supervisor user ID and the child or subordinate user ID may be prepared and 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-described storage setting process 164, but either one or both may be implemented as required by the system.

(Method 1)
The first method is to determine the relationship between the user and other users (parent-child relationship or the relationship between superiors and subordinates) according to conditions determined in advance by the system. This is a method of permitting other users (children or subordinates) to save settings.
In this method, when there is a request from a user (parent or boss) to make a save setting for another user (child or subordinate), the other user is not notified of the request (the other user). Give permission to save settings). For this reason, it is particularly effective when the relationship between users is a parent and child, especially when the child is a certain age or less (for example, an age group for which the parent does not want to store history of information for adults, such as 13 years or less). It is.
Therefore, here, a case where the relationship between users is a parent and child and the child is 13 years old or less will be described as an example.

First, the parent user logs in from the user terminal 110 with his / her user ID and password, and accesses a storage setting application page prepared in advance. A user (child) to be saved and set is designated on the save setting application page (a child user ID or the like is input) and transmitted to the server 130.
When the save setting application is received, the save setting process 164 checks the relationship between the user who made the save setting application and the designated user. Specifically, for example, referring to the user database in FIG. 20 described above, the addresses of both users are the same, and the age (determined from the date of birth) of the users (parents) is more than a certain value (for example, It is determined whether the other user (child) is under 13 years old (determined from the date of birth).
If the condition is met (the relationship between the users is a parent and child and the child is 13 years old or younger), the child user ID is registered in the user ID of the user (parent) that can be stored in the user database. To do.
Thereafter, when the user (parent) logs in to the server 130 with his / her user ID and password, the user (parent) can access the storage setting page of the other user (child) and set the child search history storage setting. .

Note that the above condition is an example, and it may be determined that the child is a parent or child by matching the telephone number, last name, IP address, or the like in addition to or instead of the address.
Moreover, you may judge that it is a parent by the age difference with a child. When the conditions exemplified here are used, it is not always the parent and child that meet the conditions. For example, grandparents and grandchildren, relatives living together, and older brothers who are separated may be used. That is, strictly speaking, it is determined whether or not the user is in a position where the other users (children under 13 years old) can freely perform storage restrictions.

Further, the server 130 (here, the user ID that can be saved and set in the user database) stores in advance that the child is a parent and child, and the parent can enter the child's saving setting page without applying the saving setting application described above. It may be accessible.
Alternatively, the above-described storage setting application and the parent-child relationship may be determined each time the parent desires to store the child search history without registering the parent-child relationship in a database or the like.

(Method 2)
In the second method, when there is a save setting application request specifying another user (child or subordinate) from a user (parent or supervisor), the other user (child or subordinate) is notified of that, Ask for consent to save settings by the user (parent or boss). If consent is obtained, the storage setting can be performed thereafter.
In this method, permission for storage setting is given to the user (parent or supervisor) on the condition of consent from another user (child or subordinate). Therefore, it is effective when the relationship between users is a relationship between a boss and a subordinate, or when the child is a parent or child whose age is a certain age (for example, 14 years or older).

First, similarly to the above-described method 1, the user (parent or boss) inputs the user ID of another user (child or subordinate) on the save setting application page and transmits it to the server 130.
When the storage setting application is received, the storage setting process 164 notifies the designated user (child or subordinate) that the user (parent or supervisor) desires the restriction. Specifically, for example, the notification is sent by sending an e-mail describing the URL to the page for consent together with the notification text to the e-mail address of the other user (child or subordinate). Alternatively, a notice text and a URL link to the consent page may be displayed on the user-dedicated page (FIG. 4 above) of the other user (child or subordinate).

  When the other user (child or subordinate) accesses the consent page and gives consent (for example, by clicking the “Agree” button displayed on the consent page), the user (parent or supervisor) in the user database. The user IDs of children and subordinates are registered in the user IDs that can be saved. Thereafter, as in the method 1 described above, when the user (parent or supervisor) logs in to the server 130 with his / her user ID and password, he / she accesses the save setting page of the other user (child or subordinate), Save settings for children and subordinates.

  In the second method, when the child was 13 years old or younger, the parent made the storage setting for the child according to the above-mentioned method 1, but the child was later not subject to age restriction (to 14 years old). Can also be used. In this case, for example, when the child is 14 years old, the child is notified of the consent page described above, and when the child gives consent, the parent can continue to set the storage of the child.

It is the figure which showed an example of the system configuration using the search history preservation | save system of this embodiment. It is the figure which respectively showed the main items of (a) search word database, (b) site history database, (c) preservation | save setting database. It is the figure which respectively showed the main item of (a) label database and (b) evaluation item database. It is an example of composition of a user exclusive page transmitted to a user terminal in this embodiment. It is an example of the search result page in a search engine. It is the flowchart which showed an example of the flow of a search word preservation | save process. It is the flowchart which showed an example of the flow of site history preservation | save processing. It is an example of a site history list page. It is an example of a page for site history printing. It is an example of a search word list page. It is an example of the page for search word printing. It is an example of a site history edit page. It is an example of a label list page. It is an example of a label edit page. It is an example of an evaluation item list page. It is an example of an evaluation item edit page. It is an example of a search history setting page. It is an example of a prohibition word setting page. It is an example of a prohibition URL setting page. It is the figure which showed the main items of the user database.

Explanation of symbols

110 User terminal 112 Browser 114 Cookie
120 Internet 130 Server 140 Search system 142 Search database 144 Search process 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 storage process 163 Search history transmission processing 164 Storage setting processing 165 Label registration / update processing 166 Evaluation item registration / update processing 400 User-specific page 410 Search box 411 Search text box 412 “Search” button 413 “Search history” tab 420 Search history setting area 421 “pause automatic saving” link 422 “search history setting” link 430 left navigation 440 calendar display area 450 recently 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 input text box 472 “Registration” 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 Movement 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 frequency display field 825 “Re-search” 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 printing page 901 Page title display field 902 Date table Display field 903 Search word display field 910 Site history display field 911 Site name display field 912 Site URL display field 913 Site summary 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 frequency 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 column 1110 Search word list display column 1111 Search word display column 1112 Site history number display column 1113 Search type display column 1114 Search date display column 1200 Site history edit page 210 “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 Optional 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 display area 1331 Label name display field 1332 Site history number display field 1333 “Edit” link 1400 Label edit page 1410 Label display field before change 1420 Label input field after change 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 Display Order Selection Link 1530 Evaluation Item List Area 1531 Evaluation Item Name Display Field 1532 Site history number display column 1533 “Edit” link 1600 Evaluation item edit page 1610 Evaluation item display column 1620 before change Evaluation item input column 1630 “Save” button 16 0 “Delete” button 1700 Search history setting page 1710 Storage limit setting area 1711 Detailed setting field 1712 Display number setting field 1713 Filtering setting field 1714 “Save setting” button 1720 Bookmark import area 1721 Path input field 1722 “Reference ”Button 1723“ Import ”button 1800 Prohibited word setting page 1810 Prohibited word input field 1820 Prohibited word deletion field 1830 Prohibited word list 1900 Prohibited URL setting page 1910 Prohibited URL input field 1920 Prohibited URL deletion field 1930 Prohibited URL list

Claims (9)

A search history storage system in which a user terminal stores a search history using a search engine in a server,
Storage setting storage means for storing search history storage restriction conditions;
When a search word search word is received from the searcher's terminal, the search word storage means stores the search word in the history storage means as a search history in accordance with the stored restriction condition;
When receiving from the terminal of the searcher that the search result site corresponding to the search word is accessed, the access information to the site is associated with the search word according to the stored restriction condition Site history storage means for storing in the history storage means as a search history above,
In response to a request from the searcher's terminal, the searcher's search history is read from the history storage means, and the search word associated with each other in the read search history and the access information to the site are displayed. Search history transmission means for transmitting the list page to the terminal;
When the evaluation information indicating the evaluation of one site indicated by the access information of the search history is received from the searcher's terminal, the search word and the one site associated with the search word Evaluation registration means for setting the evaluation information in the corresponding search history in the history storage means for associating the access information with the evaluation information ,
The search history transmission means displays the search word associated with each other in the search history read from the history storage means, the access information to the site, and a list page displaying the evaluation of the site of the searcher. Send to device,
A search history storage system characterized by that. The search history storage system according to claim 1 ,
The search history transmission means further reads out the search history of the searcher in response to a request from a terminal of a viewer different from the searcher, and displays the list page based on the read search history as the terminal of the viewer Send to
A search history storage system characterized by that. The search history storage system according to claim 1 or 2 ,
The storage restriction condition of the storage setting storage means includes a prohibited word,
The search word storage means does not store the search condition including the prohibited word,
The site history storage means does not store site information including the prohibited word;
A search history storage system characterized by that. The search history storage system according to any one of claims 1 to 3 ,
The storage restriction condition of the storage setting storage means includes a prohibited URL,
The site history storage means does not store site information including the prohibited URL;
A search history storage system characterized by that. The search history storage system according to any one of claims 1 to 4 ,
An edit page for editing the search history is transmitted to the searcher's terminal,
The search history transmission means receives the edited content set in the editing page from the searcher's terminal, and updates the corresponding item of the search history in the history storage means with the edited content;
A search history storage system characterized by that. The search history storage system according to any one of claims 1 to 5 ,
A storage setting unit for storing the storage restriction condition in the storage setting storage unit;
A storage setting page for setting the storage restriction condition of the searcher is transmitted to the searcher's terminal,
The storage setting means receives the storage restriction condition set in the storage setting page from the searcher's terminal, and stores the received storage restriction condition in the storage setting storage means;
A search history storage system characterized by that. The search history storage system according to claim 6 ,
The storage setting means further comprises:
A storage setting application page is transmitted to a terminal of an applicant different from the searcher to specify the searcher to which the setting of the storage restriction condition is applied, and the applicant and the storage setting application page Whether or not the specified searcher is in a predetermined relationship, and when the applicant and the specified searcher are in the predetermined relationship, the storage of the specified searcher Transmitting the storage setting page for setting a restriction condition to the applicant's terminal, and storing the storage restriction condition set in the storage setting page in the storage setting storage unit;
A search history storage system characterized by that. A search history storage system in which a user terminal stores a search history using a search engine in a server,
Storage setting storage means for storing search history storage restriction conditions;
When a search word search word is received from the searcher's terminal, the search word storage means stores the search word in the history storage means as a search history in accordance with the stored restriction condition;
When receiving from the terminal of the searcher that the search result site corresponding to the search word is accessed, the access information to the site is associated with the search word according to the stored restriction condition Site history storage means for storing in the history storage means as a search history above,
In response to a request from the searcher's terminal, the searcher's search history is read from the history storage means, and the search word associated with each other in the read search history and the access information to the site are displayed. Search history transmission means for transmitting the list page to the terminal;
A storage setting unit for storing the storage restriction condition in the storage setting storage unit;
A storage setting page for setting the storage restriction condition of the searcher is transmitted to the searcher's terminal,
The storage setting unit receives the storage restriction condition set in the storage setting page from the searcher's terminal, and stores the received storage restriction condition in the storage setting storage unit;
The storage setting means further comprises:
A storage setting application page is transmitted to a terminal of an applicant different from the searcher to specify the searcher to which the setting of the storage restriction condition is applied, and the applicant and the storage setting application page Whether or not the specified searcher is in a predetermined relationship, and when the applicant and the specified searcher are in the predetermined relationship, the storage of the specified searcher Transmitting the storage setting page for setting a restriction condition to the applicant's terminal, and storing the storage restriction condition set in the storage setting page in the storage setting storage unit;
A search history storage system characterized by that. A program for causing a computer to function each means of the search history storage system according to any one of claims 1 to 8 .