Browse Prior Art Database

Automatic bookmark replacement

IP.com Disclosure Number: IPCOM000124575D
Original Publication Date: 2005-Apr-28
Included in the Prior Art Database: 2005-Apr-28
Document File: 2 page(s) / 144K

Publishing Venue

IBM

Abstract

Proposed is a way to automatically and intelligently replace bookmarks that resolve to broken links by automatically searching the internet in the background using keywords for the link content as search criteria when a broken link is discovered. This solution would display the first URL listed and notify the user (perhaps with a pop up dialog box) that a new link has been found, list the additional search result links for the user to select if the one shown is not desired, and automatically save the new link and delete the old one when the user confirms that the URL displayed in the browser is the correct one.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Automatic bookmark replacement

Often when someone tries to revisit a link stored in a bookmark, the link is broken; the content is no longer available at the same location. In this situation, one would likely search for the information elsewhere on the internet using one of the search engines, and save a new bookmark when one finds a URL with the information needed. The user would also delete the old bookmark to the broken link.

Consider the user wants to visit a bookmark that's named "Java* Tutorial", that is the location of a Java tutorial on the internet. The bookmark is selected and the link is broken. The scenario described requires the following steps: point the browser to a search engine URL type in the search criteria (This will often be what is chosen to name the bookmark - in this case the search would be for "java tutorial".), find another link to the information (which is often the first link listed), save a new bookmark, then remove the old bookmark. This is tedious and occurs often.

Existing technology will notify the user when a link has changed or is broken, but it does not prevent the sequence of steps described above. Another technology that attempts to solve the same problem saves a copy of the html in a database when you create a link, so the content is available if the link disappears (similar to enabling the browser to view a link 'offline'). This does not address the situation when content is dynamic, and the user wants a link to live information.

There are many bookmark managers available that notify about broken links and provide tools for organizing, searching and sharing bookmarks - some do all of this but none of them automate the steps listed above.

The mechanism provided would implement an event handler that responds when the http client receives a return code indicating a broken link. The program would perform ...