JP4767159B2 - LINK INFORMATION MANAGEMENT PROGRAM, LINK INFORMATION MANAGEMENT DEVICE, AND LINK INFORMATION MANAGEMENT METHOD - Google Patents

Description

  The present invention relates to a link information management program, a link information management device, and a link information management method.

  A web browser, which is one of application software used when browsing a web page, is provided with various functions for easily browsing a desired web page. As one of the functions, a bookmark for storing the position (URL) of a frequently viewed web page is used.

By saving the URL in the bookmark, the user can save the trouble of inputting the URL or searching.
In order to save the URL in the bookmark, for example, a bookmark adding function provided in the browser is operated in a state where a Web page to be added to the bookmark is opened. Thereby, the title of the Web page is stored in the bookmark together with the URL of the Web page.

  When the user wishes to view the saved web page, the user selects the title saved in the bookmark with a mouse or the like. Thereby, it is possible to move quickly to the Web page.

By the way, in recent years, feed readers are becoming popular as other application software for easily browsing a desired Web page.
The feed reader has a feed list that stores a feed position (hereinafter referred to as a feed URL) in which summary information of a certain Web page is described.

  The feed is described in an XML format such as RSS (Rich Site Summary) or Atom provided from a web page. For example, a web page feed related to news includes the title, date, and description (description) of each news article as summary information. The URL of each article is included.

  This feed reader periodically and automatically circulates the feed URL stored in the feed list, and acquires the above-described summary information. Also, it has a function to manage unread / read articles by the user, and if there is an unread article in the acquired summary information, it is determined that the web page has been updated and notified to the user . This eliminates the need for the user to periodically visit the site and check for updates, and can efficiently browse only the updated information.

Here, as a feed distribution method (creation method), there are the following.
1) Officially distributed by the Web page administrator.
In the case of a Web page in which a feed is prepared and distributed on the administrator side, a feed icon is installed in the page to prompt the user to use it. Users who wish to subscribe to this page can save the feed URL in their feed list, for example, by dragging and dropping the icon to the feed reader.

2) Delivered by a third party separate from the Web page manager.
A third party creates and distributes summary information from a web page using an automatic feed creation program or the like for a web page or the like that does not deliver a feed on the administrator side. In many cases, this summary information is distributed on a server separate from the original Web page.

  However, even if the Web page or feed that you wish to subscribe to is registered in the bookmark or feed list, the URL of the Web page or feed changes due to the movement of the Web page or the stop of the feed distribution service. May be. In this case, when the user notices, it is necessary to re-search for a new URL of the web page or feed and re-register the change in the bookmark or feed list. However, there is a problem that such maintenance work is very time-consuming.

To deal with such problems, for example, the management server that manages bookmarks circulates URLs stored in bookmarks, detects inaccessible URLs, finds URLs causing broken links, and automatically A method for updating to a new URL is known (for example, see Patent Document 1).
JP 2001-273185 A

However, feed lists have unique problems that are different from bookmarks.
First, the following problem 1 exists due to the property that the feed browses only updated information.

  [Problem 1] Even if the link is not broken, the feed of the page that has stopped being updated becomes unnecessary and should be deleted from the feed list. For example, a problem that occurs frequently when using an automatically generated feed, but if you have registered and used a feed that was automatically generated from the “New Arrival Information for FY2005” page, the page will be updated when it changes to FY2006 Is no longer needed. In many cases, there is a new “2006 new arrival information” page, which needs to be re-registered. At this time, the system must automatically determine that the re-registration destination is the 2006 page. In this way, it is not sufficient to detect a broken feed simply by detecting a broken link as in the prior art. Not only the change in the year given as an example, there are various types of phenomena that cause the feed to stop functioning and its re-registration destinations, and it is not easy to automatically handle all of them by specifying rules.

  In addition, due to the nature of multiple feeds such as official feeds and automatically generated feeds by third parties for the same web page (there are multiple ways to view the same web page), the following issues There are a few.

  [Issue 2] For example, when an automatically generated feed is used for a Web page without an official feed, when the distribution of the official feed starts, we want to change to that page. However, even if the official feed comes out, the automatically generated feed that has been used so far does not stop functioning and can be used as it is. The method is unaware of the emergence of official feeds.

  [Issue 3] When there are multiple feeds, it is difficult to automatically determine which feed is the best (which feed should be registered in each feed list) (manually, manually) Even if it is judged, it is not easy for beginners with low skills to judge at a glance before using it continuously).

  The present invention has been made in view of the above points, and a link information management program and link information management that allow a user to easily know better quality unknown feeds and reduce the work load of the feed list maintenance work. An object is to provide a device and a link information management method.

In order to solve the above problem, the present invention provides a link information management program for causing a computer to execute the processing shown in FIG.
The computer 1 that executes the link information management program has the following functions.

A list management DB (database) 2 manages, for each user, a user list having position information of a document that the user wishes to subscribe to and position information indicating the position of the outline of the document.
The change means 3 receives the change data regarding the change of the outline position information transmitted from the terminal device 4 used by a certain user, and changes the outline position information of the user list of this user.

  Based on a predetermined discrimination rule, the notification discriminating means 5 sends the summary position information to the terminal device used by another user who has the changed summary position information or the position information of the document corresponding to the changed summary position information in the user list. It is determined whether or not to notify the change.

When the notification determination unit 5 determines that notification is to be performed, the notification unit 7 notifies the terminal device 6 used by another user of notification information including the change of the summary position information.
According to such a link information management program, the user list is managed for each user by the list management DB 2. The change means 3 receives change data relating to the change of the outline position information transmitted from the terminal device 4 used by a certain user, and the outline position information of this user list is changed. Based on a predetermined determination rule, the notification determination unit 5 transmits the changed outline position information or the position information of the document corresponding to the changed outline position information to the terminal device used by another user having the user list in the outline position information. It is determined whether or not to notify the change. When it is determined by the notification determination unit 5 that notification is to be performed, the notification unit 7 notifies the terminal device 6 used by another user of notification information including a change in the summary position information.

  Further, in order to solve the above-described problem, when the change data regarding the change of the summary position information indicating the position of the summary of the document that the user desires to subscribe is transmitted from the terminal device used by a certain user, In the list management DB for managing the user list having the position information and the summary position information for each user, the summary position information of the user list of the user is changed and changed based on a predetermined determination rule. It is determined whether or not the change of the summary position information should be notified to the terminal device used by another user having the position information of the document corresponding to the summary position information or the changed summary position information in the user list. When it is determined that notification is to be made, notification information including the change of the summary position information is notified to the terminal device used by the other user. Link information management method, characterized in that there is provided.

  According to such a link information management method, when change data is received, the summary position information of the user list of the user who transmitted the change data in the list management DB is changed. Then, based on a predetermined determination rule, it is determined whether or not the change of the summary position information should be notified to a terminal device used by another user who has the position information of the document corresponding to the changed summary position information in the user list. Is done. When it is determined that notification is to be made, notification information including a change in the summary position information is notified to a terminal device used by another user.

  In order to solve the above-mentioned problem, a list management DB that manages a user list having position information of a document that the user desires to subscribe and summary position information indicating a position of the outline of the document for each user, Based on a change means for receiving change data related to the change of the summary position information transmitted from a terminal device used by a certain user and changing the summary position information of the user list of the user, and a predetermined determination rule, Whether the summary position information should be notified to the terminal device used by another user who has the changed position information or the position information of the document corresponding to the changed position information in the user list. Notification determining means for determining the terminal device used by the other user when the notification determining means determines that the notification should be notified, Link information management apparatus characterized by comprising a notification means for notifying the notification information including the change of main location information is provided.

  According to such a link information management apparatus, the same processing as that of the computer that executes the link information management program is executed.

  In the present invention, based on a predetermined discrimination rule, a feed change made by a certain user is notified to a terminal device used by another user. This allows the user to easily know the presence of an associated unknown feed even when a feed continues to function. In addition, when multiple feeds exist for the same Web page, the system can automatically determine the feed quality using the usage status of the entire user, and notify the user of changes to a better feed. can do. Therefore, the user can easily perform maintenance work for the purpose of improving the quality of the feed list as well as correcting the broken link. Even a novice user can perform the same maintenance work as a highly skilled user from the beginning.

  In particular, when supplementary information (usage status of other users, etc.) supplementing the content of the change is explicitly added to the notification information and notified, the change notified by the user himself / herself is reflected in his / her user list. It is possible to obtain a material for determining whether or not it should be.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
First, the outline of the invention applied to the embodiment will be described, and then the specific contents of the embodiment will be described.

FIG. 1 is a schematic diagram showing an invention applied to the embodiment.
The link information management program can cause the computer 1 to execute processing as shown in FIG.

  The list management DB 2 has a user list (position URL) indicating position information (home URL) of a document (Web page) that each user desires to subscribe to and position information (feed URL) indicating the position of the outline (feed) of this document. (Feed list) is managed for each user (for each user ID).

  The change means 3 receives change data regarding the change of the outline position information transmitted from the terminal device 4 used by a certain user (a certain user is logged in using the user ID), and an outline of the user list of this user Change location information.

  Based on a predetermined discrimination rule, the notification discriminating means 5 gives an outline to a terminal device used by another user who has in the user list position information of a document (described in the position information) corresponding to the changed outline position information. It is determined whether or not a change in position information should be notified.

When the notification determination unit 5 determines that notification is to be performed, the notification unit 7 notifies the terminal device 6 used by another user of notification information including the change of the summary position information.
Although two terminal devices 4 and 6 are shown in FIG. 1, the number of terminal devices is not particularly limited in the present invention.

  According to such a link information management program, the user list is managed for each user by the list management DB 2. The change means 3 receives change data relating to the change of the outline position information transmitted from the terminal device 4 used by a certain user, and the outline position information of the list of a certain user is changed. Whether notification position change should be notified to the terminal device used by another user who has the position information of the document corresponding to the changed summary position information in the user list based on a predetermined determination rule by the notification determination means 5 It is determined whether or not. When it is determined by the notification determination unit 5 that notification is to be performed, the notification unit 7 notifies the terminal device 6 used by another user of notification information including a change in the summary position information.

Hereinafter, embodiments of the present invention will be specifically described.
FIG. 2 is a block diagram illustrating the information management system according to the embodiment.
In the information management system, the server 20 and a plurality of terminal devices 40 a, 40 b, 40 c, and 40 d are connected via the network 10.

The server 20 manages a feed list for each user.
Each of the terminal devices 40a, 40b, 40c, and 40d accesses the server 20 and refers to the feed list. Further, it is connected to the Internet 14 and acquires a feed from a Web page on the Internet 14 based on the feed list.

  When the server 20 receives change data related to registration, update or deletion of a feed URL from the terminal device 40a used by a certain user, the server 20 reflects the change in the feed list of the user. Then, the change is notified to the terminal devices 40b, 40c, and 40d used by other users as necessary. When another user accepts the change of the feed URL, the change is reflected in the feed list of the other user. In this way, a change in the feed URL of one user can be shared with other users.

FIG. 3 is a diagram illustrating a hardware configuration example of the terminal device.
The entire server 20 is controlled by a CPU (Central Processing Unit) 121. A random access memory (RAM) 122, a hard disk drive (HDD: Hard Disk Drive) 123, a graphic processing device 124, an input interface 125, and a communication interface 126 are connected to the CPU 121 via a bus 127.

  The RAM 122 temporarily stores at least part of an OS (Operating System) program and application programs to be executed by the CPU 121. The RAM 122 stores various data necessary for processing by the CPU 121. The HDD 123 stores an OS and application programs. A program file is stored in the HDD 123.

  A monitor 11 is connected to the graphic processing device 124. The graphic processing device 124 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 121. The input interface 125 is connected to the keyboard 12 and the mouse 13. The input interface 125 transmits a signal sent from the keyboard 12 or the mouse 13 to the CPU 121 via the bus 127.

  The communication interface 126 is connected to the network 10. The communication interface 126 transmits and receives data to and from other servers and terminal devices via the network 10.

  With the hardware configuration as described above, the processing functions of the present embodiment can be realized. Although FIG. 3 shows the hardware configuration of the server 20, the terminal devices 40a, 40b, 40c, and 40d can be realized with the same hardware configuration. In order to perform information management in a system having such a hardware configuration, the following functions are provided in the server 20.

FIG. 4 is a block diagram illustrating functions of the server and the terminal device.
In FIG. 4, the terminal device 40c and the terminal device 40d are not shown.
The server 20 includes a feed list management DB 21, a change history management DB 22, a rule management DB 23, a change detection unit 24, a notification determination unit 25, a notification information selection unit 26, a window information creation unit 27, and a response management unit 28. .

The feed list management DB 21 stores a feed list of users who use the information management system.
The change history management DB 22 stores a change history management table for managing the history of feed URLs changed by change data for changing the feed URL.

  The rule management DB 23 includes a rule table in which operation (processing) conditions of the change detection unit 24, the notification determination unit 25, the notification information selection unit 26, the window information creation unit 27, and the response management unit 28 are defined, and a user-specific rule table. A user rule table in which operating conditions are defined is stored. The contents of the feed list, change history management table, rule table, and user rule table will be described later.

  The change detection unit 24 receives change data from each terminal device. Then, it confirms that the change data received based on the rule table is the change data to be detected, and updates the feed list in the feed list management DB 21. The update contents differ depending on the change data. Then, the change data is passed to the notification determination unit 25.

When receiving the change data, the notification determination unit 25 refers to the feed list and the rule table, and determines whether or not the change should be notified to other users.
The notification information selection unit 26 selects a user who notifies the change (hereinafter referred to as “notification target user”) when the change is to be notified to another user, and records necessary information in the change history management table. To do.

  The window information creation unit 27 creates window information for each notification target user based on the change history management table, and transmits the window information to the terminal device used by the notification target user. The window information will be described later.

  When the response management unit 28 receives the response information transmitted from the terminal device used by the notification target user according to the window information, the response management unit 28 reflects the response content included in the response information in the feed list and the change history management table. . Then, the window information creating unit 27 is made to create window information using a user rule table as necessary.

  The terminal devices 40a and 40b have change notification units 41a and 41b, update candidate reception units 42a and 42b, response information transmission units 43a and 43b, and application execution units 44a and 44b, respectively. Hereinafter, each function of the terminal device 40a will be described representatively.

The change notification unit 41a notifies the server 20 of change data created by, for example, a user operation.
The update candidate receiving unit 42a receives the window information and passes the window information to the application execution unit 44a.

Upon receiving the response information from the application execution unit 44a, the response information transmission unit 43a transmits the response information to the response management unit 28.
The application execution unit 44a has a GUI (Graphical User Interface), activates a feed reader in accordance with the user's operation of the terminal device 40a, and displays the feed reader on the monitor of the terminal device 40a. Moreover, response information is created according to the user's operation of the terminal device 40a, and is sent to the response information transmission unit 43a.

FIG. 5 is a diagram showing a feed reader.
The feed reader 45 includes a feed list display unit 46, a headline display unit 47, and a content display unit 48.

A feed web page title 461 (such as “F2 press release” in FIG. 5) of the feed stored in the feed list is displayed in the feed list display unit 46.
The feed reader 45 periodically accesses each feed URL on the feed list and acquires a feed. Further, the feed reader 45 manages unread and read feed articles. If there is an unread article, the web page title 461 is bolded as a new event notification, and an unread article is displayed on the right side of the title. Display a number.

  The headline display unit 47 displays the headline 471 of the article on the Web page. The same title as the Web page title is displayed in the header portion of the headline display portion. New articles are distinguished from other articles by, for example, displaying a symbol 472 or the like.

  When the user selects the headline 471 by clicking with the mouse or the like, the content of the Web page is displayed on the content display unit 48. Then, the headline 471 is already read.

  On the feed list display unit 46, the user can freely edit his / her own feed list, such as adding a new feed, deleting unnecessary feeds, and editing property information of an existing feed.

  FIG. 6 is a diagram showing a feed property editing screen. This screen is displayed, for example, by selecting (right-clicking) the Web page title of the feed list display unit 46 with a mouse.

The property 461a includes fields for a feed URL, a title, and a Web page home URL.
The feed URL, which is summary position information, is stored in the feed URL column.

  In the title column, the title of the Web page displayed on the feed list display unit 46 is stored. The feed URL and title can be arbitrarily edited by the user.

The Web page home URL field stores the URL of the home (top page) of the Web page.
When the user presses the OK button, the editing content is confirmed. Also, the content of editing is canceled by pressing a cancel button. When a change occurs due to editing, the application execution unit 44a passes this change content to the change notification unit 41a as change data.

Next, the contents of the change data, feed list, change history management table, and rule table will be described.
FIG. 7 is a diagram showing change data.

  In the change data 311a, columns of parameters, before change, after change, and user ID are provided in this order from the left side. The parameter column is provided to identify the change state. In the user ID column, the user ID that transmitted the change data is set. Information arranged in the horizontal direction of each column is associated with each other.

The columns before and after the change are further provided with columns for title, home URL, and feed URL for identifying the changed data.
In the parameter column, attributes (addition, editing, deletion) of changed data are set.

In the column before change, the title, home URL, and feed URL of the Web page before change are set.
When the parameter column is “addition”, “null” is set for each item before the change. When “edit” or “delete” is set in the parameter column, data to be changed or deleted is set in the column before the change, respectively.

In the changed column, the title, home URL, and feed URL of the changed Web page are set.
The changed user ID is set in the user ID column.

FIG. 8 is a diagram showing a feed list.
The feed list 21a stores a list for each user ID (user list). Each user ID list is associated with feed URL (xmlUrl = ...), Web page title (title = ...), and home URL (htmlUrl = ...) as property information of one feed. In addition, information of a configuration for dividing each feed into folders as shown in FIG. 5 is described in the XML format.

FIG. 9 is a diagram showing a change history management table.
In the change history management table 22a, No. , Notification destination (user ID), notification information, notification No. , Reaction date and time, reaction, processing columns are provided. The notification information column further includes an old title, an old home URL, an old feed URL, a new title, a new home URL, a new feed URL, and additional information columns, and information arranged in the horizontal direction of each column. They are associated with each other to form individual management information.

No. In this column, serial numbers for all notifications (numbers for identifying one notification for one notification target user) are set.
In the notification destination (user ID) column, the user ID of the notification target user is set.

  In the notification information column, the old title, the old home URL, the old feed URL, and the new title, new home URL, and new feed URL corresponding to the old title, the old home URL, and the old feed URL respectively registered by the notification target user are recorded.

  In the additional information column, additional information defined in a rule table, which will be described later, is transmitted to the user together with the URL as information for reference when determining whether the change notified by the user should be reflected in his / her feed list. Is set.

  Notification No. In the column of, a number for identifying a discovery common to all notifications made in response to one feed discovery, and a number for identifying a single notification to be notified to the same notification target user regarding the discovery A combination is set.

The date and time when response information from the terminal device used by the notification target user is received is set in the response date and time column.
The response content (update / reject / hold) from the terminal device used by the notification target user is set in the reaction column.

In the processing column, “completed” is set when the response content is updated or rejected and when new management information for the notification destination is created.
FIG. 10 is a diagram illustrating a rule table.

  The rule table 23a includes columns for detection target (corresponding target), notification determination target, notification target user, notification target data, and additional information, and the information arranged in the horizontal direction of each column is associated with each other. ing. The rule table 23a defines a rule 230a to be applied when change data is received.

  In the detection target column, information related to the feed that is the detection target of the change detection unit 24, for example, “feed addition change data”, “feed edit change data”, “feed deletion change data”, and the like are set.

  In the notification determination target column, information related to the determination criterion of the notification determination unit 25, for example, “when the new feed URL of the change data is unknown among the feed URLs specifying the same home URL” is set. Is done.

In the notification target user column, the type of user to be notified, for example, “all users who register a feed URL having the same home URL as the change data” is set.
In the column of notification target data, data to be transmitted to the user to be notified, for example, “the old feed URL currently registered by the notification target user and the new feed URL newly discovered (changed data)” and the like are set. Is done.

Information to be transmitted together with the notification target data, for example, “discoverer's user ID” or the like is set in the additional information column.
Various other information can be considered. Statistics related to the usage status of the entire user using various log information that can be taken by the server, profile information registered by the user himself (for example, interested keywords, user IDs of trusted users, etc.), Any information that can be useful for the user's judgment regarding the URL change, such as information (seasonal keywords) obtained from an external Internet service or e-mail, may be used.

Next, the operation of the server 20 in the information management system will be described.
In the following, the operation when the server 20 receives the change data transmitted by the terminal device 40a and the notification target user uses the terminal device 40b will be described.

FIG. 11 is a flowchart showing the operation of the server.
First, the change detection unit 24 performs detection processing (step S1).
Next, the notification determination unit 25 performs determination processing (step S2).

Next, the notification information selection unit 26 performs data creation processing (step S3).
Next, the window information creation unit 27 performs a data transmission process (step S4).
Next, it is judged whether the response management part 28 received the response information from the terminal device 40b (step S5). When the response information from the terminal device 40b has not been received (No in step S5), the response information is waited. When the response information from the terminal device 40b is received (Yes in step S5), the response management unit 28 performs a response reflection process (step S6). Above, operation | movement of the server 20 is complete | finished. Note that the flowchart of FIG. 11 shows a process when each process does not end halfway, and the case where the process ends halfway will be described in detail in the description of each process below.

Next, the detection process performed by the change detection unit 24 will be described.
FIG. 12 is a flowchart showing the detection process.
First, change data from the terminal device 40a is received (step S11).

  Next, the corresponding user ID list in the feed list 21a is rewritten based on the change data (step S12). For example, when the change data of FIG. 7 is newly added to FIG. 8, <outline text = “A news” title = “A news” xmlUrl = “http://a-news.jp/” is added at the end of FIG. news.rss "htmlUrl =" http://a-news.jp/index.html> "is added.

Next, with reference to the detection target column of the rule table 23a, it is determined whether or not the change data matches the detection target (step S13).
If the change data does not match the detection target (No in step S13), the operation is terminated. For example, when only the rule table shown in FIG. 10 is stored, and “edit” or “delete” is set in the parameter field of the change data, the operation is terminated.

  On the other hand, when the change data matches the detection target (Yes in step S13), the change data is passed to the notification determination unit 25 (step S14). For example, when the rule table shown in FIG. 10 is stored and “addition” is set in the parameter column of the change data, the change data is passed to the notification determination unit 25. This completes the detection process.

Next, the determination process performed by the notification determination unit 25 will be described.
FIG. 13 is a flowchart showing the discrimination process.
For example, the notification determination target of the rule table 23a shown in FIG. 10 is “when the new feed URL of the change data is unknown as a feed specifying the same home URL”. The feed URL and the user ID are extracted, and the home URL “http://a-news.jp/index.html” of the change data is extracted in the feed list 21a and the user IDs of all the users and the corresponding feed URLs are extracted. Then, notification target user data is created (step S21).

FIG. 14 is a diagram showing notification target user data.
The notification target user data 25a includes No. Column of title, home URL, feed URL, and user ID are provided, and information arranged in the horizontal direction of each column is associated with each other.

No. A number for identifying the order of processing is set in this field.
In the title, home URL, and feed URL fields, the title, home URL, and feed URL extracted from the feed list 21a of each user are recorded.

The user ID is recorded in the user ID column.
Returning to FIG. 13, the description will be continued.
Next, it is determined whether the notification condition is satisfied (step S22). In the created notification target user data 25a, the same as the change data feed URL “http://a-news.jp/news.rss” (the data of the user ID other than the user ID “kawafuji” of the change data). ) Determine if it exists.

  If the notification condition is not satisfied (No in step S22), the operation of the server 20 is terminated. On the other hand, when the notification condition is satisfied (Yes in step S22), for example, the known feed URL for the home URL “http://a-news.jp/index.html” is “http://html2rss.jp/RSS”. .Jsp? Url = http: //a-news.jp/index.html ”, and the change data feed URL“ http://a-news.jp/news.rss ”is the first URL to appear. If it is found, the user data to be notified is passed to the notification information selection unit 26 (step S23). This completes the discrimination process.

Next, the data creation process performed by the notification information selection unit 26 will be described.
FIG. 15 is a flowchart showing data creation processing.
First, referring to the notification target user column of the rule table 23a, a user is selected (step S31). For example, the notification target user of the rule table 23a shown in FIG. 14, the user having the user ID “keroron” and the user having the user ID “tascal” are selected in the notification target user data shown in FIG.

Next, the user ID of the selected user is stored in the change history management table 22a (step S32).
Next, the contents of the notification target user data 25a are reflected in the notification information column of the change history management table 22a (step S33). Further, since the additional information in the rule table 23a shown in FIG. 10 is “discoverer's user ID”, “discoverer's user ID = kawafuji” is stored in the additional information column (step S34). This completes the data creation process.

Next, data transmission processing performed by the window information creation unit 27 will be described.
FIG. 16 is a flowchart showing data transmission processing.
First, the change history management table 22a is referred to, and notification information including an old title, an old home URL, an old feed URL, a new title, a new home URL, a new feed URL, and additional information is created for each notification target user (step). S41).

Next, window information for displaying the information created in step S41 is created (step S42).
And window information is transmitted in anticipation of the transmission timing to the terminal device 40b (each terminal device used by the notification target user) (step S43). The transmission timing is not particularly limited. For example, when the terminal device 40b activates the feed reader, the transmission timing is transmitted immediately. In addition, when the terminal device 40b does not activate the feed reader, it is transmitted when the feed reader is activated. This completes the data transmission process.

When the application execution unit 44b receives the window information, an update notification window for displaying the notification information is displayed on a monitor provided in the terminal device 40b.
FIG. 17 is a diagram showing an update notification window.

  The update notification window 51 includes a comment display section 52, a current property information display section 53, an update information display section 54, an update button 55, a reject button 56, and a hold button 57.

  The comment display section 52 displays the contents of the additional information. In FIG. 17, the user ID of the discoverer is displayed together with a predetermined sentence. At this time, the user ID is displayed as a link, and when the user clicks the link using a mouse or the like, the terminal device 40b accesses a user profile DB (not shown) of the server 20, and the user's ID is displayed. The profile information may be referred to.

  The current property information display section 53 displays the current title (before change), the home URL, and the feed URL. Further, the updated information display section 54 displays the changed title, home URL, and feed URL. Of these, the part to be changed (character part of feed URL as an example in FIG. 17) is displayed with the color, font size, etc. changed to improve the notification to the user.

  Each title, home URL, and feed URL of the current property information display unit 53 and update information display unit 54 are displayed as links. When the user clicks the link using a mouse or the like, the link destination is accessed. The information associated with the link, for example, the home URL of the link destination if the home URL is displayed.

  The user presses the update button 55 when updating the information displayed on the current property information display unit 53 to the information displayed on the update information display unit 54. If the information displayed on the current property information display unit 53 is not changed to the information displayed on the update information display unit 54, the reject button 56 is pressed. In addition, when the decision is put on hold, the hold button 57 is pressed. When any one of these buttons is pressed, the application execution unit 44b sends response information including any one of response types of update, rejection, and hold to the response information transmission unit 43b.

  Here, when the hold button is pressed, a re-notification condition is added to the response information. One or a plurality of re-notification conditions may be used, and one or a plurality of re-notification conditions can be selected. In the case of a plurality of buttons, the button may be a pull-down menu method and may be selected from the pull-down menu method.

In the present embodiment, three options (update / reject / hold) are provided. However, the present invention is not limited to this, and other options may be provided.
Next, the response reflection process performed by the response management unit 28 will be described.

FIG. 18 is a flowchart showing the response reflection process.
First, when response information is received from the response information transmission unit 43b, the response type of the response information is specified. That is, it is determined whether the response type is update, rejection, or hold (step S51).

  If the response type is update (update in step S51), the feed list 21a is updated (step S52). Then, necessary items are recorded in the reaction date / time, reaction, and processing fields of the change history management table 22a (step S53).

  When the response type is rejection (rejection in step S51), necessary items are recorded in the reaction date and time, reaction, and processing columns of the change history management table 22a without updating the feed list 21a (step S54).

  When the response type is “pending” (pending in step S51), necessary items are recorded in the reaction date and time columns of the change history management table 22a (step S55). The data for re-notification is held, and then a re-notification process is performed (step S56).

Thus, the response reflection process ends.
Next, the re-notification process will be described.
FIG. 19 is a flowchart showing the re-notification process.

  First, the response management unit 28 refers to the re-notification rule table in which the re-notification condition is set, monitors the change history management table 22a, and determines whether or not the re-notification condition is satisfied (step S61). The re-notification condition may be, for example, a rule common to all users, such as “half of notification users according to notification registered a new URL for this change”, or may be set individually by each user. If the re-notification condition is not satisfied (No in step S61), the process waits until the re-notification condition is satisfied. When the re-notification condition is satisfied (Yes in step S61), the response management unit 28 checks the list of re-notification target users in the feed list 21a to determine whether or not the feed URL before the change has been changed. (Step S62). When the feed URL before the change has been changed (Yes in step S62), the re-notification is stopped, “finished” is filled in the processing column of the change history management table 22a (step S62a), and the operation ends. When the feed URL before the change has not been changed (No in step S62), the notification No. in the change history management table 22a. New management information in which the column is updated is created (step S63). In the example shown in FIG. 1 is put on hold. 6 is the re-notification. Notification No. Is the second notification of the same URL notification, the re-notification is “1-1” with respect to the previous notification No “1-0”. No. The processing column of No. 1 is No. 1. When “6” re-notification is created, “done” is stored.

Thereafter, the notification information is passed to the window information creation unit 27 (step S64).
The re-notification process is thus completed.
Next, the re-notification rule table will be described.

  The re-notification rule table 23b includes columns for re-notification conditions, re-notification contents, and additional information. Since the contents to be set are the same as those in the rule table 23a, the description thereof is omitted. The re-notification rule may be common to all notifications, or each user may be able to specify each notification.

Next, each process described above will be described using specific examples.
In this example, there is no official feed in the past, and distribution of the official feed is started on a web page called “A News” that each user has registered and used an automatically generated feed, and the user with the user ID “kawafuji” This is an example of finding and registering an official feed. Based on this discovery, other users who have used the automatically generated feed are notified of the presence of the official feed.

  The home URL of “A News” is “http://a-news.jp/index.html”, and the feed URL of the automatically generated feed is “http://html2rss.jp/RSS.jsp?url=http://” a-news.jp/index.html ”, and the feed URL of the official feed is“ http://a-news.jp/news.rss ”. Further, it is assumed that the rule table is set as shown in the rule table 230a of FIG.

The current change data transmitted to the server 20 by the user with the user ID “kawafuji” is as the change data 311a shown in FIG.
Next, the operation of this example will be described.

The operation of the server 20 when the change notification unit 41a transmits the change data 311a illustrated in FIG. 7 to the server 20 when the terminal device 40a is added by operation will be described.
When the change detection unit 24 receives the change data from the terminal device 40a, it rewrites the feed list of the user ID “kawafuji”.

FIG. 20 is a diagram illustrating a feed list of a specific example.
An underlined portion 211b is added to the feed list 21a based on the change data.
Next, the change detection unit 24 determines whether the change data is a change in accordance with the rule 231a. In this specific example, since the change conforms to the rule 230 a, the change data is passed to the notification determination unit 25.

  The notification determination unit 25 refers to the rule 230a and creates notification target user data of the home URL “http://a-news.jp/index.html” from the change data and the feed list 21a. In the following description, it is assumed that the notification target user data 25a shown in FIG. 14 has been created.

  Next, the notification determination unit 25 determines whether or not the change data feed URL “http://a-news.jp/news.rss” has already appeared in the notification target user data 25a. In this specific example, since “http://a-news.jp/news.rss” has not been issued, the notification target user data 25 a is passed to the notification information selection unit 26.

  Next, the notification information selection unit 26 refers to the rule 230a, selects all users other than the user ID “kawafuji”, and records the information of the notification target user data 25a in the notification information column of the change history management table 22a. To do.

FIG. 21 is a diagram showing a change history management table at the end of the data creation process.
The contents shown in FIG. 9 are recorded in the notification destination (user ID) column and the notification information column of the change history management table 22a.

Thereafter, the window information creation unit 27 creates window information and transmits it.
And whenever the response management part 28 receives the response information from the terminal device which a notification object user uses, it judges a response classification (update, rejection, hold), and performs the process mentioned above.

FIG. 22 is a diagram illustrating a change history management table when response information is received.
Since the user with the user ID “tascal” has selected the update, the processing is completed.

Since the user with the user ID “keroron” has selected suspension, the response management unit 28 refers to the re-notification rule table and monitors the change history management table 22a.
FIG. 23 is a diagram illustrating a re-notification rule table.

  According to the re-notification rule table 23b, the re-notification condition is “a majority of users updated based on the notification information”. The content of the re-notification adds information on how many people have been updated as additional information to the same URL change notification information as the previous time.

  After that, when the response management unit 28 determines that the response column of the majority of the notification target users in the change history management table 22a has been updated, the response management unit 28 checks the current feed list of the user ID “keroron” After confirming that it is the same as the feed URL “http://html2rss.jp/RSS.jsp?url=http://a-news.jp/index.html”, the change history management table 22a Notification number of user ID “keroron”. New management information “1-1” is created, and “updated number = 38/50” is recorded in the additional information column. No. “Done” is entered in the column of the management information processing of “1” (previous notification No. “1-0”).

  After that, additional information (for example, “Re-notification: 38 out of 50 people have updated this feed URL”) is added to the notification information previously notified to the user ID “keroron”. The window information is transmitted to the terminal device used by the user with the user ID “keroron”.

FIG. 24 is a diagram illustrating the change history management table after the re-notification process is executed.
Thereafter, when there is a response from the terminal device with the user ID “keroron”, the response reaction process is continued.

When all the user's processing fields are “completed”, the operation is terminated.
FIG. 25 is a diagram illustrating a change history management table after the re-notification process is completed.
As described above, according to the information management system of the present embodiment, a change in a feed URL of a certain user is notified to a terminal device used by another user. As a result, the information on the change of the feed URL can be shared between the users, and the user can easily know the existence of a feed unknown to him / her. Because it is based on manual changes, it is more reliable than conventional automatic detection methods. In addition, in the conventional method, when the change of the feed URL is automatically detected by the server, it is difficult to target a functioning feed instead of a broken link. However, in this embodiment, a feed for a certain Web page is already a feed. Even if it is registered in the list and the feed is functioning, the user can easily know the new feed URL for the feed. Therefore, it is possible to easily switch from an automatically generated feed to an official feed.

  In addition, by reflecting this change of the feed URL in each list of the feed list, it is possible to reduce the load of maintenance work. In addition, when each user reflects a change (update, deletion) of the feed URL in his / her list of the feed list, it is only necessary to press a button (update button 55, reject button 56) on the update notification window 51. Therefore, it is possible to easily update the feed list.

  In addition, by providing the rule table 23a and setting information that conforms to the rule as information to be notified, the user can receive only information on changes necessary for himself from many changes. Further, by separately setting a rule for each user and making it a detection target of the change detection unit 24, for example, only when the feed URL is changed from a specific (high skill) user desired by the user, Detailed customization for each user, such as receiving change information, is also possible.

  Also, if there are multiple feeds for the same web page, you can use many judgments instead of one person's judgment, such as feed registration status and change notification acceptance rate for the entire user. The feed quality can be determined such that “the feed being used is a good quality feed”.

  Furthermore, by adding additional information such as the usage status of the entire user to the window information notified to the user, the user can more easily determine whether or not the notified feed URL needs to be updated. For example, as in the present embodiment, by adding information such as a user ID that is a source of information, the reliability of the notification information can be improved and the update can be promoted.

In the present embodiment, the case where the user list is a feed list has been described. However, the information management system can also be applied to a bookmark.
FIG. 26 is a diagram illustrating change data when the information management system according to the first embodiment is applied to a bookmark.

In the bookmark change data 511a, “null” is set in the feed URL field both before and after the change.
FIG. 27 is a diagram illustrating a rule table when the information management system according to the first embodiment is applied to a bookmark.

  In the detection target column of the bookmark rule table 23c, information on a bookmark to be detected by the change detection unit 24, for example, "change data added to bookmark", "change data of bookmark change", "change data of bookmark deletion". Is set.

In the notification determination target column, information related to the determination criterion of the notification determination unit 25, for example, “unknown as home URL for the same title” or the like is set.
In the notification target user column, the type of user to be notified, for example, “all users who have registered bookmarks with the same title” or the like is set.

By applying such change data 511a and rule table 23c to the information management system of the present embodiment, the same effects as described above can be obtained.
Next, an information management system according to the second embodiment will be described. A description of the same matters will be omitted, focusing on the differences from the first embodiment described above.

  In the information management system of the second embodiment, the property “edit” (change of the feed URL on the property edit screen) in which the user has explicitly changed from a certain feed URL to a certain feed URL is detected. To do. The point of sending notification information to other users when the number of people who have edited from a certain feed URL to a certain feed URL exceeds a predetermined number is different from the first embodiment.

  In the following, the automatically generated feed of “2005 new arrival page” was registered. However, it is necessary to re-register in the automatically generated feed of “2006 new arrival page” because the year has changed. An example will be described.

FIG. 28 is a block diagram illustrating a server according to the second embodiment.
The server 20a according to the second embodiment has a counter management DB 29 in which a person counter table for counting the number of persons who have changed the feed URL for a certain home URL is stored.

FIG. 29 is a diagram showing a number counter table.
The number-of-people counter table 29a has columns for a feed before change, a feed after change, and a counter.

  In the feed field before the change, the URL of the feed URL field before the change data is changed (in FIG. 29, “http://http2rss.jp/RSS.jsp?url=http://.../news/2005 ") Is recorded.

  In the post-change column, the URL in the post-change feed URL column (in FIG. 29, “http://http2rss.jp/RSS.jsp?url=http://.../news/2006 ") Is recorded.

  In the counter column, the number of users (counter value) who changed the feed URL set in the pre-change feed column to the feed URL set in the post-change feed column is set.

FIG. 30 is a diagram illustrating a rule table according to the second embodiment.
A rule 232a is defined in the rule table 23a.
In the detection target field of the rule 232a, a rule "feed edit change data" is defined.

  In the notification determination target field of the rule 232a, a rule is defined that “if the number of people who have edited the same feed URL exceeds 15”. As a result, the notification determination unit 25 determines whether or not the number of received change data of the same feed edit exceeds 15 (predetermined number).

  In the notification target user field of the rule 232a, a rule "all users who have registered an old feed URL" is defined. Accordingly, the notification information selection unit 26 sets all users who have registered the old feed URL included in the change data in their own feed list 21a as notification information notification destinations.

  A rule “new and old feed URL” is defined in the notification target data column of the rule 232a. As a result, the notification information selection unit 26 uses the old and new feed URLs as the content of the notification information.

  In the additional information column of the rule 232a, a rule “number of edited users” is defined. As a result, the notification information selection unit 26 creates additional information that “the number of editors has exceeded 15”.

Next, the operation of the information management system according to the second embodiment will be described.
First, when the change detection unit 24a receives change data from the terminal device 40a, the change detection unit 24a determines whether the change is in accordance with the rule 232a, that is, whether the change data is editing.

FIG. 31 is a diagram illustrating a specific example of change data.
The change data is from the old feed URL “http://html2rss.jp/RSS.JSP?url=http://.../news/2005” and the new feed URL “http://html2rss.jp/RSS.JSP”. ? Url = http: //.../news/2006 ", corresponding changes.

Therefore, the list of users who have transmitted the change data in the feed list 21a is rewritten based on the change data.
Next, the notification determination unit 25 increments the counter value of the number of people counter table 29a. Thereafter, the counter value is counted, and when the counter value exceeds 15, the notification target user data is passed to the notification information selection unit 26.

  The notification information selection unit 26 refers to the notification target user data, and registers the feed URL "http://http2rss.jp/RSS.jsp?url=http://.../news/2005". Select all users other than the user. Then, the window information having the notification information having the old and new feed URLs and the additional information “more than 15 editors” is created and transmitted to the terminal device used by the corresponding user.

  According to the information management system of the second embodiment, the same effect as the information management system of the first embodiment can be obtained. Even if the feed automatically generated from the page of fiscal year 2005 does not work in fiscal 2006, a user's notice is shared with other users, and all users can replace the feed of fiscal year 2006. Because it is based on manual changes, the change coverage is wider than conventional automatic detection methods.

Next, an information management system according to a third embodiment will be described. The description of the same matters will be omitted, focusing on the differences from the first embodiment described above.
The information management system according to the third embodiment is characterized in that, when the server detects a broken link of the feed URL, etc., it requests an excellent user to find a new feed URL and notifies the other user of the result. This is different from the first embodiment.

FIG. 32 is a block diagram illustrating a server according to the third embodiment.
The server 20b according to the third embodiment includes a broken link detection unit 30, an excellent user ranking calculation unit 31, an alternative feed survey request unit 32, and a user profile management DB 33 in which a user profile table is stored. Yes.

The broken link detection unit 30 periodically checks the list of each user in the feed list 21a and detects the presence or absence of a broken link.
The excellent user ranking calculation unit 31 periodically calculates the ranking of excellent users who are skilled in the maintenance work of the feed list and stores it in the user profile table. The ranking is calculated by, for example, the acceptance rate of the window information for each user ID (the ratio of the response information of “update” being returned in the number of windows notified to other users by the discovery of the user). Information necessary for calculating the acceptance rate can be obtained from the change history management table 22a.

  The alternative feed survey requesting unit 32 specifies a user ID for requesting an alternative feed survey based on the acceptance rate, and requests an alternative feed survey. Specifically, a user with the highest acceptance rate is searched, and request information for requesting a search for an alternative feed is transmitted to the terminal device used by the user with the user ID. If the user is not found, the user with the next highest acceptance rate is searched and the user is asked to investigate the alternative feed. Thereafter, the same operation is repeated until a user to be requested is found.

FIG. 33 shows a user profile table.
The user profile table 33a includes a user No. , Notification destination (user ID), password, name, e-mail address, and excellent user ranking columns are provided, and information arranged in the horizontal direction of each column is associated with each other.

User No. In this column, a number for identifying the order registered in the user profile table 33a is set.
A user ID is set in the user ID column.

A password for each user ID is set in the password column.
The name of the user who uses the user ID is set in the name column.
A mail address for each user is set in the mail address column.

In the excellent user ranking column, ranks are recorded in order of the acceptance rate.
FIG. 34 illustrates a rule table according to the third embodiment.
A rule 233a is defined in the rule table 23a.

  In the detection target field of the rule 233a, a rule "response to a broken link discovery request" is defined. Thereby, the change detection unit 24 sets the parameter column of the change data transmitted from the terminal device used by the user requested by the alternative feed survey requesting unit 32 as “detection response” to be detected.

  In the notification determination target field of the rule 233a, a rule “discovery of alternative feed” is defined. As a result, the notification determination unit 25 determines whether the change data of the response from the requested user includes the description of the new feed URL column or whether the link can be connected.

  In the notification target user field of the rule 233a, a rule "all users who have registered old feed URLs that are broken links" is defined. Thereby, the notification information selection unit 26 selects all users who have registered the old feed URL.

  A rule “new and old feed URL” is defined in the notification target data column of the rule 233a. As a result, the notification information selection unit 26 uses the old and new feed URLs as the content of the notification information.

  In the additional information column of the rule 233a, a rule of “discoverer's user ID and ranking of excellent user ranking” is defined. Thereby, the notification information selection unit 26 creates additional information in which the user ID requested by the alternative feed survey requesting unit 32 and the ranking recorded in the excellent user ranking column of the user profile table 33a are inserted.

Next, the operation of the information management system according to the third embodiment will be described.
First, the broken link detection unit 30 periodically accesses URLs in the feed list 21a of all users and detects broken URLs. Here, http: // a. Assume that rss has found a broken link.

Next, the excellent user ranking calculation unit 31 periodically calculates the acceptance rate and stores it in the user profile table 33a.
Next, the alternative feed survey requesting unit 32 specifies the terminal device used by the user who requests the alternative feed survey based on the acceptance rate, and requests the alternative feed survey.

  After that, when the change detection unit 24 receives change data from the terminal device used by the user who requested the investigation of the alternative feed, it is determined whether or not the change is in accordance with the rule 233a, that is, the feed URL “http: //a.rss”. It is determined whether or not the response is a response to the broken link discovery request.

FIG. 35 is a diagram illustrating a specific example of change data.
In this case, since it is a response to the broken link discovery request of the feed URL “http: //a.rss”, the list of users who requested the search of the feed list 21a is rewritten based on the change data.

  Next, the notification determination unit 25 determines whether the change data includes an alternative new feed URL. In this case, since the alternative feed URL “http: //b.rss” is included, it is confirmed that the connection can be made to “http: //b.rss”, and then the notification target user data is passed to the notification information selection unit 26. .

The notification information selection unit 26 selects all user IDs that have registered the feed URL “http: //a.rss”.
Then, the window information creation unit 27 indicates that the feed URL “http: //a.rss” is broken and there is “http: //b.rss” as the alternative URL, and that the additional user information includes the excellent user ranking 1. The window information for notifying that the discovery is made by the user “kawafuji” is transmitted to the terminal device of the corresponding user.

  According to the information management system of the third embodiment, the same effect as the information management system of the first embodiment can be obtained. Even if the user is unaware of the broken link of the feed URL, based on the discovery of the system, it is possible to notify a good user who is skilled in the maintenance of the feed list of the broken link, and even the novice user shares the result maintained by the good user can do.

Next, an information management system according to a fourth embodiment will be described. The description of the same matters will be omitted, focusing on the differences from the first embodiment described above.
The information management system according to the fourth embodiment is such that when a certain user adds a feed URL, based on the usage status of each user, if there is a better feed URL, the added user is notified. This is different from the embodiment.

FIG. 36 is a diagram illustrating a rule table according to the fourth embodiment.
A new rule 234a is defined in the rule table 23a.
In the detection target field of the rule 234a, a rule "change data for adding a feed" is defined. Thereby, the change detection unit 24 sets the addition of a new feed URL of the user as a detection target.

  In the notification determination target field of the rule 234a, a rule is defined that “80% or more of users register a feed URL different from the change data for the same home URL as the change data”. Thereby, the notification determination unit 25 determines whether or not there is a user who has registered another feed for the home URL of the added feed, and if there is, the ratio of the other feed to the home URL. Whether it is above a certain level is determined.

  A rule “detection source user” is defined in the notification target user field of the rule 234a. Accordingly, the notification information selection unit 26 selects a user who has added a feed URL and sent change data as a selection target.

  In the notification target data field of the rule 234a, a rule of “an old feed URL added by a user and a new major feed URL between existing users” is defined. Further, in the additional information column of the rule 234a, a rule “the ratio of users who register new feed URLs among existing users” is defined. As a result, the notification information selection unit 26 creates notification information, for example, “For feed http: //a.rss, http: //ax.rss is the major (80% of users are using)”. To do.

Next, the operation of the notification determination unit 25 when the change data is received will be described.
FIG. 37 is a diagram illustrating a specific example of the change data, and FIG. 38 is a flowchart illustrating the operation of the notification determination unit when the change data is received.

  First, notification target user data registered as a feed URL of the home URL “http: //aa.html” is created (step S81). Then, the ratio of the number of registered users for each feed URL is calculated from the notification target user data (step S82). Then, it is determined whether there is another URL registered by 80% or more of the users with a feed URL other than “http: //a.rss” of the change data (step S83). If there is no other feed URL registered by 80% or more of users (No in step S83), the operation is terminated. On the other hand, when 80% or more of the users have registered the feed URL “ax.rss” as a feed of the home URL “http: //aa.html” (Yes in step S83), the notification information selection unit 26 is notified. User data is passed (step S84).

  According to the information management system of the fourth embodiment, the same effect as that of the information management system of the first embodiment can be obtained. When adding a new feed, the usage status of other users can be used to feed back the existence of a better unknown feed to the user. As a result, even a novice and low-skilled user can use a high-quality feed from the start of use.

Next, an information management system according to a fifth embodiment will be described. The description of the same matters will be omitted, focusing on the differences from the first embodiment described above.
In the information management system of the fifth embodiment, the server periodically checks the list of each user in the feed list, and considers the usage status of all users, and recommends the deletion of a feed having a low usage value. This is different from the first embodiment.

FIG. 39 is a block diagram illustrating a server according to the fifth embodiment.
The server 20c of the fifth embodiment has an access log management DB 34 that stores an access log in which a history of feed URLs accessed by each user is recorded.

FIG. 40 is a diagram showing an access log.
The access log 34a includes a log No. User ID, time, and feed URL fields are provided, and information arranged in the horizontal direction of each field is associated with each other.

Log No. In this column, a number for identifying the order registered in the access log 34a is set.
The user ID is recorded in the user ID column.

In the time column, the time when the feed URL is accessed is recorded.
The feed URL accessed by the user is recorded in the feed URL column.
Next, the operation of the information management system according to the fifth embodiment will be described.

  First, the change detection unit 24b compares the feed list 21a with the access log 34a, and extracts a feed URL that has not been accessed for a certain period of time. And the notification discrimination | determination part 25 produces notification object user data about discovered feed URL, and also checks the access condition of each user. When the number of users who have not accessed for a certain period of time is more than a certain percentage, a notification that recommends deletion from the feed list is made.

  According to the information management system of the fifth embodiment, the same effect as that of the information management system of the first embodiment can be obtained. Although it is useful as much as possible to easily improve the quality of the feed list by notifying unnecessary feeds by notifying a user that individual users have lost access, the information management system of the present embodiment further provides The low use value of the feed can be determined based on the usage status of other users, such as “not only a certain user but many users do not use”.

The preferred embodiment of the present invention has been described in detail above, but the present invention is not limited to the specific embodiment.
In each of the above-described embodiments, the case where the feed list 21a is managed has been described. However, the present invention is not limited to this, and can be applied to the case where, for example, a browser bookmark is managed.

  The above processing functions can be realized by a computer (by causing the computer to execute a predetermined link information management program). In that case, a program describing the processing contents of the functions that the server should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape. Examples of the optical disc include a DVD (Digital Versatile Disc), a DVD-RAM, a CD-ROM (Compact Disc Read Only Memory), and a CD-R (Recordable) / RW (ReWritable). Examples of the magneto-optical recording medium include MO (Magneto-Optical disk).

  When distributing the program, for example, a portable recording medium such as a DVD or a CD-ROM in which the program is recorded is sold. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  A computer that executes the link information management program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

(Appendix 1)
A list management DB that manages, for each user, a user list having position information of a document that the user wishes to subscribe to and position information indicating the position of the outline of the document;
Change means for receiving change data relating to a change in the summary position information transmitted from a terminal device used by a certain user, and changing the summary position information in the user list of the user;
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Notification discriminating means for discriminating whether or not to notify the change of
A notification means for notifying the terminal device used by the other user of notification information including a change in the summary position information when the notification determination means determines that the notification should be made;
Link information management program characterized by functioning as

(Supplementary note 2) The link information management program according to supplementary note 1, wherein the notification means adds supplementary information supplementing the content of the change to the notification information for notification.
(Supplementary note 3) The link information management program according to supplementary note 2, wherein the supplementary information is information that promotes a change in the summary position information.

  (Supplementary Note 4) When the computer receives response information in response to the notification information transmitted from the terminal device used by the other user, the summary position information of the user list of the other user is The link information management program according to appendix 1, wherein the link information management program is caused to function as response management means for changing to the outline position information transmitted from the terminal device used by a user.

(Supplementary Note 5) The re-notification desired by the re-notification requesting user transmitted from the terminal device used by the re-notification requesting user who wishes to re-notify the notification information among the other users. When receiving response information for requesting re-notification of the notification information together with a condition, the computer further functions as a re-notification condition management DB for storing the re-notification condition,
The response management unit determines whether or not the re-notification condition is satisfied, and when the re-notification condition is satisfied, the notification information to the terminal device used by the user who wants to re-notify the notification unit The link information management program according to appendix 4, wherein the re-notification is requested.

(Supplementary note 6) The link information management program according to supplementary note 5, wherein the notifying unit adds supplementary information that prompts a change of the summary position information when re-notifying the notification information.
(Additional remark 7) The said notification means specifies the user of notification object from the user who has the positional information on the said document in the said user list based on the predetermined notification rule, and the said user of notification object uses the said notification information The link information management program according to appendix 1, wherein the terminal device is notified.

  (Additional remark 8) Whether the said notification discrimination | determination means is more than a predetermined number of said other users who are making the change which corresponds to the change content of the said summary position information contained in the said change data with reference to said list management DB The link information management program according to supplementary note 1, wherein it is determined that notification should be made when the number of other users who are making a change that matches the change content of the summary position information is greater than or equal to a predetermined number.

(Supplementary note 9) Link break detection means for periodically checking the respective user lists to detect the summary position information that is no longer accessible to the position information of the document.
Functioning as request means for transmitting request information for requesting a change to new summary position information replaced with the summary position information, which is no longer accessible to the position information of the document, to the terminal device used by a predetermined user. The link information management program according to supplementary note 1, characterized by:

  (Additional remark 10) The said request means is the said notification information with the said highest ratio based on the user profile which calculated the ratio of the user who changed the said summary position information according to the said notification information which the said notification means notified 10. The link information management program according to appendix 9, wherein the request information is transmitted to the terminal device used by the sender.

  (Additional remark 11) The said notification determination means is whether the said summary position information of the said change data transmitted from the said terminal device which the said user uses differs from the said summary position information of the said user list of the said other user If the information is different, the notification means notifies the terminal device used by the user who transmitted the change data of the summary position information of the user list of the other user. The link information management program according to appendix 1, which is characterized.

(Additional remark 12) Let the said computer function as access log storage DB which stores the access log to the said summary position information for every said user,
The detection means detects the summary position information that has not been accessed for a predetermined period based on the user list and the access log,
When the notification determination unit determines that the notification determination unit should be notified, the notification target user is a user who has the summary position information in the user list, and the notification target user uses the summary position information. The link information management program according to appendix 9, which is notified to a terminal device.

(Additional remark 13) The said summary position information is feed information, The link information management program of Additional remark 1 characterized by the above-mentioned.
(Supplementary Note 14) Upon receiving change data regarding a change in outline position information indicating a position of an outline of a document that the user desires to subscribe, transmitted from a terminal device used by a certain user, the position information of the document and the outline position Change the summary position information of the user list of the user in the list management DB for managing the user list having information for each user,
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Determine if you should be notified of changes,
When it is determined that notification should be made, the terminal device used by the other user is notified of notification information including the change of the summary position information.
A link information management method characterized by the above.

(Supplementary Note 15) A list management DB that manages, for each user, a user list having position information of a document that the user desires to subscribe and summary position information indicating a position of the outline of the document;
Change means for receiving change data related to the change of the summary position information transmitted from a terminal device used by a certain user, and changing the summary position information of the user list of the user;
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Notification discriminating means for discriminating whether or not to notify the change of
A notification means for notifying the terminal device used by the other user of notification information including a change in the outline position information when the notification determination means determines that the notification should be performed;
A link information management device comprising:

(Supplementary note 16)
A list management DB that manages, for each user, a user list having position information in which positions related to documents that the user wishes to subscribe to are recorded;
Change means for receiving change data relating to a change in the position information transmitted from a terminal device used by a user, and changing the position information in the user list of the user;
Notification for determining whether or not the change of the position information should be notified to the terminal device used by another user who has the position information corresponding to the changed position information in the user list based on a predetermined determination rule Discrimination means,
A notification means for notifying the terminal device used by the other user of notification information including the change of the position information when the notification determination means determines that the notification should be made;
Link information management program characterized by functioning as

It is a schematic diagram which shows the invention applied to embodiment. It is a figure which shows the information management system of embodiment. It is a figure which shows the hardware structural example of a terminal device. It is a block diagram which shows the function of a server and a terminal device. It is a figure which shows a feed reader. It is a figure which shows the property edit screen of feed. It is a figure which shows change data. It is a figure which shows a feed list. It is a figure which shows a change log | history management table. It is a figure which shows a rule table. It is a flowchart which shows operation | movement of a server. It is a flowchart which shows a detection process. It is a flowchart which shows a discrimination | determination process. It is a figure which shows notification object user data. It is a flowchart which shows a data creation process. It is a flowchart which shows a data transmission process. It is a figure which shows an update notification window. It is a flowchart which shows a response reflection process. It is a flowchart which shows a re-notification process. It is a figure which shows the feed list of a specific example. It is a figure which shows the change log management table at the time of completion | finish of data creation processing. It is a figure which shows the change log | history management table when response information is received. It is a figure which shows a re-notification rule table. It is a figure which shows the change log management table after execution of a renotification process. It is a figure which shows the change log | history management table after completion | finish of a renotification process. It is a figure which shows the change data at the time of applying the information management system of 1st Embodiment to a bookmark. It is a figure which shows the rule table at the time of applying the information management system of 1st Embodiment to a bookmark. It is a block diagram which shows the server of 2nd Embodiment. It is a figure which shows a people counter table. It is a figure which shows the rule table of 2nd Embodiment. It is a figure which shows the specific example of change data. It is a block diagram which shows the server of 3rd Embodiment. It is a figure which shows a user profile table. It is a figure which shows the rule table of 3rd Embodiment. It is a figure which shows the specific example of change data. It is a figure which shows the rule table of 4th Embodiment. It is a figure which shows the specific example of change data. It is a flowchart which shows operation | movement of the notification discrimination | determination part when change data is received. It is a block diagram which shows the server of 5th Embodiment. It is a figure which shows an access log.

Explanation of symbols

1 Computer 2 List management DB
3 Changing means 4, 6, 40a to 40d Terminal device 5 Notification determining means 7 Notifying means 20, 20a to 20c server 21 Feed list management DB
21a Feed list 22 Change history management DB
22a Change history management table 23 Rule management DB
23a rule table 23b user rule table 24, 24a, 24b change detection unit 25 notification determination unit 25a notification target user data 26 notification information selection unit 27 window information creation unit 28 response management unit 29 counter management DB
29a Number of people counter table 30 Broken link detection unit 31 Maintainer ranking calculation unit 32 Alternative feed survey request unit 33 User profile management DB
33a User profile table 34 Access log management DB
34a Access log 41a, 41b Change notification unit 42a, 42b Update candidate reception unit 43a, 43b Response information transmission unit 44a, 44b Application execution unit 45 Feed reader 51 Update notification window 230a-234a Rule 311a Change data

Claims (6)

Computer
A list management DB that manages, for each user, a user list having position information of a document that the user wishes to subscribe to and position information indicating the position of the outline of the document;
Change means for receiving change data related to the change of the summary position information transmitted from a terminal device used by a certain user, and changing the summary position information of the user list of the user;
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Notification discriminating means for discriminating whether or not to notify the change of
A notification means for notifying the terminal device used by the other user of notification information including a change in the summary position information when the notification determination means determines that the notification should be made;
Link information management program characterized by functioning as   The link information management program according to claim 1, wherein the notification means adds supplementary information supplementing the content of the change to the notification information for notification.   When the computer receives response information responding to the notification information transmitted from the terminal device used by the other user, the user uses the summary position information of the user list of the other user. 2. The link information management program according to claim 1, wherein the link information management program functions as response management means for changing to the summary position information transmitted from the terminal device. When the change data related to the change of the outline position information indicating the position of the outline of the document that the user desires to subscribe is received from the terminal device used by a certain user, the change information includes the position information of the document and the outline position information. In the list management DB that manages the user list for each user, the summary position information of the user list of the user is changed,
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Determine if you should be notified of changes,
When it is determined that notification should be made, the terminal device used by the other user is notified of notification information including the change of the summary position information.
A link information management method characterized by the above. A list management DB that manages, for each user, a user list having position information of a document that the user wishes to subscribe to and position information indicating the position of the outline of the document;
Change means for receiving change data related to the change of the summary position information transmitted from a terminal device used by a certain user, and changing the summary position information of the user list of the user;
Based on a predetermined determination rule, the summary position information is sent to the terminal device used by another user who has changed the summary position information or the position information of the document corresponding to the changed summary position information in the user list. Notification discriminating means for discriminating whether or not to notify the change of
A notification means for notifying the terminal device used by the other user of notification information including a change in the outline position information when the notification determination means determines that the notification should be performed;
A link information management device comprising: Computer
A list management DB that manages, for each user, a user list having position information in which positions related to documents that the user wishes to subscribe to are recorded;
Change means for receiving change data related to the change of the position information transmitted from a terminal device used by a user, and changing the position information of the user list of the user;
Notification for determining whether or not the change of the position information should be notified to the terminal device used by another user who has the position information corresponding to the changed position information in the user list based on a predetermined determination rule Discrimination means;
A notification means for notifying the terminal device used by the other user of notification information including the change of the position information when the notification determination means determines that the notification should be made;
Link information management program characterized by functioning as

Images