SYSTEM AND METHOD FOR SAVING BROWSED DATA

Abstract: A system saves browsed data in a database in response to a user request by assigning a predetermined index to the data, wherein the user is not requested for any index. The system sorts indices of the data in the database and displays the sorted indices, then the system retrieves, in response to a selection of an index from the displayed indices by a user, the data corresponding to the selected index from the database. Accordingly if a user wants to save a data currently browsed, he can make store the data in the database easily only by issuing an instruction to save without specifying any index.

Description: SYSTEM AND METHOD FOR SAVING BROWSED DATA CLAIM FOR PRIORITY This application claims priority from Application No. 2000-197293, filed on May 29, 2000 in Japan and Application No. 2000-314601, filed on October 16, 2000 in Japan. FIELD A system and method for saving acquired data, and more particularly a system and method for saving acquired data browsed in a client application, such as browsed by an Internet browser. BACKGROUND A conventional computer can access and display data in an Internet using a software called browser. The conventional computer also can open a file application and store data in a file. The data on the browser can be transported to a word processing software or the like. Then a user can add an annotation to the browsed data on the word processing software or the like. The conventional computer can also send the browsed data as it is or with adding an annotation to other computer. In the above conventional computer, however, the user must specify a folder and a file name for saving the browsed data. The user must open respective applications to save, make an annotation, and send the data. Therefore, the user has to perform complex operations to save the browsed data, make an annotation therein, and send the browsed or annotated data to other computer. SUMMARY According to certain embodiments of the present invention, the present invention provides a system and method to save data, which a user wants to do with a simple operation. According to one of the embodiments, the present invention relates to a data processing system comprising data acquisition means for acquiring data; determination means for determining whether or not a user requests to save the acquired data; indexing means for assigning a predetermined index to the data requested to save, without inputting any index; and saving means for saving the requested data with the assigned index in a predetermined storage unit. According to another embodiment, the present invention relates to a data processing method comprising a data acquisition step of acquiring data; a determination step of determining whether or not a user requests to save the acquired data; an indexing step of assigning a predetermined index to the data requested to save, without inputting any index; and a saving step of saving the requested data with the assigned index in a predetermined storage unit. According to still another embodiment, the present invention relates to a computer-executable program for controlling a computer to perform data processing, said program comprising codes for causing the computer to perform a data acquisition step of acquiring data; a determination step of determining whether or not a user requests to save the acquired data; an indexing step of assigning a predetermined index to the data requested to save, without inputting any index; and a saving step of saving the requested data with the assigned index in a predetermined storage unit. Other features and advantages of the present invention will be apparent from the following description taken in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts throughout the figures thereof. BRIEF DESCRIPTION OF THE FIGURES The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. Fig. 1 is a block diagram illustrating the hardware configuration according to an embodiment of the present invention. Fig. 2 shows the functional block diagram of information processing system embodying the present invention. Fig. 3 shows the functional block diagram of information browsing system embodying the present invention. Fig. 4 is a flowchart of the main procedural steps of this embodiment. Fig. 5 is a flowchart of INITIALIZE procedure. Fig. 6 is a flowchart of MAIN-PROCESSOR. Fig. 7 is a flowchart of the procedural steps of UserAction. Fig. 8 is a flowchart of the procedural steps of CheckExisting(). Fig. 9 is a flowchart of the procedural steps of Annotate(). Fig. 10 is a flowchart of the procedural steps of Extract(). Fig. 11 is a flowchart of the procedural steps of Mgmt(). Fig. 12 is a flowchart of the procedural steps of ShowSession. Fig. 13 is a flowchart that procedural steps of ShowLinks. Fig. 14 is a flowchart of the procedural steps of ExecuteAction. Fig. 15 is a flowchart of the procedural steps of SaveContents. Fig. 16 is a flowchart of the procedural steps of WebFetch. Fig. 17 is a flowchart of the procedural steps of SendContents. Fig. 18 is a flowchart of the procedural steps of TERMINATE. Figs. 19 and 20 show examples of the knowledge structures in the knowledge base. Figs. 21 and 22 show examples content of the knowledge base. Fig. 23 shows an example content of the Domain knowledge base. Fig. 24 shows an example User Interface of this embodiment. Fig. 25 shows an example User Interface of Save UI. Fig. 26 shows example results of the knowledge structures. Fig. 27 shows an example HTML text obtained from the browser. Fig. 28 shows example results of the knowledge structures. Fig. 29 shows example modified HTML text. Fig. 30 shows example results of the knowledge structures. Fig. 31 shows an example User Interface of Hold UI. Fig. 32 shows an example User Interface of the Annotation UI. Fig. 33 shows example modified HTML text after user has performed annotations. Fig. 34 shows an example User Interface of Send UI. Fig. 35 shows an example User Interface of Extract Data UI. Fig. 36 shows example results of knowledge structures. Fig. 37 shows an example User Interface of Session UI. Figs. 38, 39, and 40 show examples User Interface of Get All Links UI. Fig. 41 shows an example Retrieve or Find UI. Fig. 42 shows an example of Properties or Attributes UI. Fig. 43 shows an example Retrieve Extracted Data or Find UI. Fig. 44 shows an example Address book UI. Fig. 45 shows an example of Properties or Attributes UI. Figs. 46 to 50 show some examples of User Settings UI. Fig. 51 is a flowchart of the procedural steps to see if any system task needs to be executed. Fig. 52 is a flowchart of the procedural steps of RemoveExpired. Fig. 53 is a flowchart of the procedural steps of CheckUpdate. Fig. 54 is a flowchart of the procedural steps of Sort by keywords. Fig. 55 is a flowchart of the procedural steps of ShowTreeView. Fig. 56 is a flowchart of the procedural steps of ProcessLeafAction. Fig. 57 is a flowchart of the procedural steps of ProcessNodeAction. Fig. 58 is a flowchart of the procedural steps of Sort by Domain. Fig. 59 is a flowchart of the procedural steps of Sort by Organization. Fig. 60 is a flowchart of the procedural steps of For Each Session, Sort KPTAction by Time. Fig. 61 is a flowchart of the procedural steps of GetPreviousYearNodes. Fig. 62 is a flowchart of the procedural steps of GetB eforeCurrMonthNodes . Fig. 63 is a flowchart of the procedural steps of GetbeforeCurrWeekNodes. Fig. 64 is a flowchart of the procedural steps of GetCurrWeekNodes. Fig. 65 is a flowchart of the procedural steps of steps S1510, S1512 SaveFileContents. Fig. 66 is a flowchart of the procedural steps of FillKPT Action. Figs. 67 and 68 are flowcharts for processing the retrieve conditions and to fetch the appropriate information. Fig. 69 shows example rules for determining the organization indices for a URL. Fig. 70 shows example rules for determining the domain indices for a URL. Fig. 71 shows a Client-Server type implementation. Fig. 72 is a flowchart of the procedural steps of ΓNITJALIZE processing of a client. Fig. 73 is a flowchart of the main procedural steps of server. Fig. 74 is a flowchart of INITIALIZE_SERVER procedure. Fig. 75 is a flowchart of the procedural steps of MATN- PROCESSOR_SERVER procedure. Fig. 76 is a flowchart of TERMINATE_SERVER procedure. Fig. 77 shows a File Server type implementation. Fig. 78 shows a Distributed Clients type implementation. Fig. 79 shows another example of Client-Server type implementation. Fig. 80 shows an example implementation in which the server acts as a proxy server. Fig. 81 shows an example web server based implementation. Fig. 82 shows an example mixed implementation of a File Server implementation and a Distributed Client implementation. Fig. 83 shows another example of implementation. Fig. 84 shows another example of compounded implementation. Fig.85 displays an example of Show All links User Interface for Distributed client implementation. Fig.86 displays an example of Show All links User Interface for Client Server implementation. Figs.87 and 88 display other examples of Show all links User Interface for external Database implementation. Fig. 89 displays an example of Session User Interface for external Database implementation. Fig. 90 displays another example of Show all links User Interface for local web information implementation. Fig. 91 displays another example of Session User Interface for File System implementation. DETAILED DESCRIPTION With reference to the figures, various embodiments of the method, system and apparatus for discovering, establishing and managing network connectivity across disparate networks will now be described in greater detail. It is to be understood that the tasks shown in the figures and described in this description can be sequenced in many different orders to achieve the desired result. The order or sequence of tasks illustrated in the figures is merely intended to be exemplary of the concepts defined herein. Fig.l is a block diagram illustrating the hardware configuration according to an embodiment of the present invention. In this figure, a central processing unit (CPU) 101 is operative to perform operations for various processing and make a logical decision or the like and further controls each composing element connected to a bus 107. A RAM 102 is used to temporarily store variables and intermediate data generated during the processing. A program from an extemal source may be loaded into the RAM 102. A ROM 103 is used to store programs, which correspond to individual flowcharts that will be described later and which are to be executed by the CPU 101, and fixed data. A keyboard (KB) 104 is used for inputting data and an instruction by a user. A mouse or other input devices may be used with the keyboard 104. Display 105 displays data and a hard disk drive (HHD) stores data of a database, a program, and the like. The bus 107 is used to transfer an address signal indicating a composing element to be controlled by the CPU 101, a control signal used for controlling each composing element and data to be exchanged between the composing equipment. Fig. 2 shows the functional block diagram of information processing system embodying the present invention. Browser 201 is used for information browsing of the Web. Filing system 202 is for filing and managing files. Document Management System 203 is for managing documents. Information Management System 204 is for managing information other than documents. KPT System interacts and acts as a controlling system as explained in detail in this embodiment to Browser 201, Filing System 202, Document Management System 203 and Information Management System 204. Knowledge Base Management 206, is the management of knowledge accessed/stored from/to the Database 206. Fig. 3 shows the functional block diagram of information browsing system embodying the present invention. The information on the Intemet 301 is browsed using multiple browsers 302, 303 simultaneously and as explained in this embodiment, KPT System 205 handles and processes them separately. Fig. 4 is a flowchart of the main procedural steps of this embodiment. The following description is for an example system, which connects to the Intemet and allows browsing, annotating, extracting and saving of the information. In step S401, initialization processes to connect to the Intemet are executed. In step S402, main function processing browsing, annotating, saving etc. of this embodiment is performed. In step S403, terminate or clean-up processing is executed. Fig. 5 is a flowchart of INITIALIZE procedure of step S401. In step S501 a check is made to determine if the browser needs to be instantiated or not. If browser is not instantiated, it is instantiated in step S502. In step S503, a new session is created. In step S504, the knowledge base is updated. The main UI of this embodiment is displayed in step S505 and the process ends. Fig. 6 is a flowchart of MAIN-PROCESSOR of step S402. In step S601, a check is made to determine if the browser was instantiated or not. If so, a new session is created in step S602 and the process proceeds to step S605, wherein the knowledge base is updated. If not, a check is made in step S603 to determine if the browser was terminated or ended. If so, the session associated with the browser is ended and proceeds to step S605. If not, a check is made in step S606 to determine if an action was performed to end the system. If so, all the current tasks are terminated in step S607 and the process returns. If not, a check is made in step S608 to determine if the user is navigating to a new URL. If so, a check is made in step S609 to confirm with the user that the current task should be terminated. If not, the process proceeds to step S610, where the navigation is aborted and the process continues to step S601. If the current task is to be ended in step S609, step S611 is executed wherein, the previous task is terminated and then a new task is created. In step S612, the knowledge structures KPTAction and KPTDocument are created. In step S613, the URL and the keywords are obtained from the Browser. A check is made in step S614 to determine if the URL data already exists in the knowledge base. If so, all the existing data for the current URL is procured from the knowledge base in step S615 and moves to step S616, where a check is made to determine if it is a RetrievedURL i.e., the user is trying to view the contents of an already stored page. If so, step S617 is executed to get the RetrieveUI message and control goes to S618. If URL data does not already exist in step S614, step S618 is executed to display the keywords, other acquired data from browser like the URL, page title etc... and other existing data if any from the knowledge base like Keep As, validity period etc... and the process proceeds to step S601. In step S608, if the user is not moving to a new URL, a check is made in step S619 to determine if any SystemTask ActL needs to be executed. If so, step S622 Execute Action (ActL) is executed and the control moves to step S605 to update the knowledge base. If not, a check is made in step S620 to determine if any User Operation was performed. If not, step S605 is executed, otherwise in step S621, the HTML text is obtained from the browser and the KPTAction and KPTDocument structures created in step S612 are updated and ExecuteAction(ActL) for the UserAction is executed in step S622 and the process moves to step S605 to update the knowledge base. For example, when the browser 201 displays an HTML page as shown in Fig. 27, the keywords embedded in the Meta Name tag (i.e., KPT, Yokohama), which are not normally displayed by the browser are extracted and displayed in the keywords field, as shown in Fig. 24. Fig. 7 is a flowchart of the procedural steps of S620 UserAction. A check is first made in step S701 to set Act equal to the User operation performed by user and to determine if Act is equal to NULL. If so, the process returns false. If it is not NULL, the process proceeds to step S702, a check is made to determine whether Act is Create New. If so, the process proceeds to step S704. If not, the process proceeds to step S703, a check is made to determine whether Act is Quick Save. If so, the process proceeds to step S704. If not, a check is made in step S705 to determine whether Act is Automatic Save. If so, the process proceeds to step S704. If not, a check is made in step S706 to determine whether Act is Save. If Act is Save, Save UI, an example of which is shown in Fig. 25, is displayed in step S707 and proceeds to step S704. If not, a check is made in step S708 to determine if the Act is Hold. If so, Hold UI, an example of which is shown in Fig. 31 is displayed in step S709 and proceeds to step S704. In step S704, a check is made to determine if the information being saved or held is already exists using CheckExistingQ, which is explained in detail later and if so, proceeds to step S720, otherwise return false. In step S708, if Act is not Hold, a check is made in step S710 to determine if the Act is Send. If so, Send UI, an example of which is shown in Fig. 34, is displayed in step S711 and the recipients (To, CC) information, Subject, Contents and/or the like are obtained from the user in step S712 and proceeds to step S720. If not, a check is made in step S713 to determine if Act is Annotate. If so, Annotate UI, an example of which is shown in Fig. 32 is displayed in step S714 and the actual Annotations executed using Annotate(), which is explained in detail later, in step S715 and proceeds to step S720. If not, a check is made in step S716 to determine if Act is Extract. If so, Extract UI, an example of which is shown in Fig. 35, is displayed in step S717 and the actual Extract information executed using Extract(), which is explained in detail later, in step S718 and proceeds to step S720. If not, Mgmt(), which is explained in detail later is executed in step S719 and proceeds to step S720. In step S720, createKS() is executed to create the associated knowledge structures, which are explained in detail later and the process returns true. Fig. 8 is a flowchart of the procedural steps of S704, CheckExisting() of this embodiment to check if the information already exists in the knowledge base or not. In step 801, the values of Keep As, Validity Range etc... are either obtained from the user or from the system settings, hi step S802, a check is made to determine whether the URL already exists. If URL does not exist, the process proceeds to step S803 where Modifystatus is set to SaveAsNew Action is set to and retums true. If URL exists, a check is made in step S 804 to determine if the information needs to be over-written (i.e., update or modify the previous information). This is done either by asking the user, whether he would like to overwrite the existing information, save as new do not save or based on the user settings as shown in Fig. 48. If so, in step S805, ModifyStatus is set to OverWriteExisting and the process returns true. If not, a check is made in step S806 to determine if the information needs to be saved as new, (i.e., without modifying the existing information, save the current information as a separate entity). If so, ModifyStatus is set to saveAsNew Action and the process returns true. If not, the process returns false. Fig. 9 is a flowchart of the procedural steps of S715 Annotate() of this embodiment and Fig. 32 shows an example user interface for Annotating a web page currently being browsed. In step S901, the user-performed operation is set to Act. A check is made in step S902 to determine if Act is Add Note. If so, the user specified memo/note is added to the selected place in step S903 and goes to step S904. If not, a check is made in step S906 to determine if the Act is Footnote. If so, the footnote number is created based on a sequence and the footnote number is added to the selected place in the page and the actual contents of the footnote are added to the end of the page in form of a table and proceeds to step S904. The notes added to the page are added based on user settings, example of which is shown in Fig. 49, to set the "annotation demarkers", "default annotation text", the color of annotation etc. The annotations are added as standard HTML tags and the results of the actual annotation for example text in Fig. 27 are shown in Fig. 33. Also, as can be seen in Fig. 32, the annotation to be added "Express Train does not Stop", is prepared using the default annotation text "My Comments" and enclosed with the annotation demarkers []. This is done to enable later for the user and/or the system to distinguish the user annotations from the actual or original HTML text. If Act is not Footnote in step S906, a check is made in step S908 to determine if the Act is Highlight. If so, a Font tag <font bgcolor = ...> is added around the selected text with the background color set to the selected color in step S909 and proceeds to step S904. If not, a check is made in step S910 to determine if the Act is Change text color. If so, a Font tag <font color=...> is added around the selected text with the foreground color set to the selected color in step S911 and proceeds to step S904. If not, a check is made in step S912 to determine if Act is Delete. If so, the tag is modified to <visible = false> to hide the selected part of the text in step S913 and proceeds to step S904. If not, a check is made in step S914 to determine if Act is Undo. If so, the last performed annotation is undone and proceeds to step S904. If not, a check is made in step S916 to determine if Act is Undo All. If so, all the annotation performed by the user on this page during this session are removed and proceeds to step S904. If not the function returns. In step S904, the modified HTML tag page is passed back to the browser, which will render and update the UI in step S905 and return to step S901. If Act is none of the ones specified in the flowchart, the function returns. Fig. 10 is a flowchart of the procedural steps of S718, Extract() of this embodiment. In step SI 001, an instance of the knowledge structure for person - KPTPerson is created. In step SI 002, the User operation is set to Act. An example User interface to describe some of the action is shown in Fig. 35. First a check is made to determine the type of Act (i.e., if Keep As, Name, Email, Phone, Fax, Notes) was input by the user (steps SI 003, S1007-S1010). This action can be performed in various ways, like first selecting the text to be extracted and pressing a predefine button, as shown in Fig. 35, or dragging and dropping the text to be extracted to the appropriate field or by right clicking on the selected text and specifying it to be the extracted data. If so, the KPTPerson knowledge structure is modified appropriately in step SI 004 and the UI gets updated in step SI 005 and the process returns to S1002. If the Act is Clear All (step S1011), all the fields are cleared in step S1012 and process proceeds to S1004. If the Act is Save (step S1013), a new action KPTAction is created of type Extract as shown in Fig. 36 and the KPTPerson is filled as associate object and the process returns. Fig. 11 is a flowchart of the procedural steps of S719 Mgmt() of this embodiment. In step SI 101, Act is set to the user-performed operation. In step SI 102, a check is made to determine if Act is NULL. If so, the process returns. If not, a check is made in step SI 103 to determine if Act is Show Sessions. If so, ShowSession() as explained later is executed in step SI 104 and the process returns. If not, a check is made in step SI 105 to determine if the Act is Show Links. If so, ShowLinks() as explained later is executed in step SI 106 and the process returns. If not, a check is made in step SI 107 to determine whether Act is Retrieve pages. If Act is to retrieve a page, the process proceeds to step SI 108 where RetrieveUI is displayed, example of which is shown in Fig. 41. If not, a check is made in step SI 109 to determine if Act is Retrieve extracted data. If so, Show Retrieve Extracted data UI is displayed, an example of which is shown in Fig. 43. If not, a check is made in step SI 111 to determine if Act is Show address book. If so, Show Address book UI is displayed, an example of which is shown in Fig. 44 and the process returns. Fig. 12 is a flowchart of the procedural steps of SI 104, ShowSession of this embodiment. In step SI 201, all the KPTAction and the associated KPTDocument are got from Knowledge Base. In step S1202, KPTAction is sorted for each session by time as explained in detail later, in Fig. 60. In step S1203, Session UI is displayed, an example of which is shown in Fig. 37 and the process returns. Fig. 13 is a flowchart that procedural steps of SI 106, ShowLinks of this embodiment. In step S1301, all the KPTAction and the associated KPTDocument are got from knowledge base. In step SI 302, a check is made to determine if the Sort Item is equal to Organizations. If so, the information is sorted by Organization, as explained in detail later in Fig. 59, in step SI 303 and proceeds to S1304, where it is displayed, an example of which is shown in Fig. 38. If not, a check is made in step SI 305 to determine if the sorting is by Domains. If so, the information is sorted by Domain, as explained in detail later in Fig. 58, in step S1306 and proceeds to step S1304, where it is displayed, an example of which is shown in Fig. 39. If not, the information is sorted by Keywords, as explained in detail later in Fig. 54, in step S1307 and proceeds to step S1304, where it is displayed, an example of which is shown in Fig. 40 and the process returns. Fig. 14 is a flowchart of the procedural steps of S622, ExecuteAction of this embodiment. In step SI 401, the next Act is got from the ActList. In step S1402, a check is made to determine if Act exists. If not, the process retums. Otherwise, in step S1403 inference is made using the knowledge base to complete the Act. A check is made in steps S1404-S1408 to determine if Act is Quick Save or Save or Hold or Automatic Save and if either one of them is true, step S1405, SaveContents() as explained later in Fig. 15. is executed and goes to step S1413. Otherwise a check is made in step S1409 to determine if Act is send. If so, SendContents(), as explained later in Fig. 17 is executed and goes to step S1413. If not, a check is made in step S1411 to check if Act is Extract. If so, the KPTAction , and the corresponding KPTPerson are added to the knowledge base in step S1412 and in step S1413 the knowledge base is updated and the process retums to step SI 401 to fetch the next action from the ActList, till there are no more action left to be processed, at which stage the process returns. Fig. 15 is a flowchart of the procedural steps of SaveContents in step S1405 of this embodiment. A check is made in step S1501 to determine if it is a SaveLink only operation. If so, process proceeds to step S1505. Otherwise, a check is made to determine if it is a SavePage contents operation in step SI 502. If so, Page PLUS is set to true in step S1504. h either case, step S1503, WebFetch() is executed, which is explained in detail later in Fig. 16, in step SI 503. In step SI 505, a check is made to determine if ModifyStatus is saveAsNew Action or not. If so, indices of KPTAction and the associated KPTDocument is determined from Knowledge Base in step SI 509 and SaveFileContents() is executed as explained in Fig.65, in step S1501. The KPTAction and KPTPerson are added to Knowledge Base in step S1506 and the process retums. If ModifyStatus is not save AsNew Action, check is made in step SI 507 to determine if it is OverWriteExisiting. If not the process retums, otherwise, in step S1511 indices of KPTAction and the associated KPTDocument is determined from Knowledge Base in step S1511 and SaveFileContents() is executed as explained in Fig.65, in step S1502. The KPTAction and KPTPerson are updated in the Knowledge Base in step SI 508 and the process retums. Fig. 16 is a flowchart of the procedural steps of WebFetch in step S1504 of this embodiment. In step S1601, HTML document obtained from the browser is opened. In step SI 602, next tag is got. In step SI 603, a check is made to determine if the end of file has been reached. If so the process retums. If not, a check is made to determine if the tag is for an embedded image, frame etc. in step SI 604. If so, step SI 605 is executed. If not, a check is made in step SI 609 to determine if PagePLUS is true and the Tag type is of LINK. If not the process retums back to step SI 602 to fetch the next tag. Otherwise, step SI 605 is executed in which a check is made to see if the contents (i.e., embedded images etc.) already exist in our knowledge base and they are up to date in step SI 605. If so, the HTML tag is edited in step SI 606 to change the absolute or original path to the local path of the system where the file exists and process retums to step SI 602. If not, a check is made to determine if the file to be fetched is a local file in step S1610. If so, the file contents are just copied, using a simple file copy command in step S1611, otherwise the contents are downloaded from the intemet in step SI 607. In either case step S 1608 is executed, wherein the knowledge base is modified to update the information downloaded etc. and process retums to step SI 602 to fetch the next tag in the HTML document. The process continues till end of file is reached at which instant the process retums. Fig. 17 is a flowchart of the procedural steps of SendContents in step S1410 of this embodiment. In step S1701, a check is made whether the contents to be sent are SendLink only. If so, a message is created with the given Link in step SI 702 and proceeds to step SI 707. If not so, a check is made to determine if the contents to be sent are SendPage (i.e., send the HTML page including the embedded images etc.), in step SI 703. If not so, a message for only top HTML is created and proceeds to step SI 707. Otherwise, Webfetch() is executed as explained in Fig.16 in step S 1705. In step S 1707, the created message is sent and the knowledge structures KPTAction and KPTDocument are added to knowledge base in step SI 708 and the process retums. Fig. 18 is a flowchart of the procedural steps of TERMINATE of step S403 of this embodiment. In step S 1801, the UI on display are closed. In step SI 802, all the current sessions are ended. In step S 1803, Knowledge base is updated. A check is made in step SI 804 to determine if browser needs to be ended or terminated. If so, the browser will be terminated in step S 1805 and the process ends. Fig. 19 shows an example of the knowledge structures in the knowledge base, (a), (b), (c) are the knowledge structure definitions for KPTConcept, KPTPerson and KPTDocument respectively. Fig. 20 shows an example of the knowledge structures in the knowledge base, (a), (b) are the knowledge structure definitions for KPTAction and KPTContent respectively. Fig. 21 shows an example content of the knowledge base, (a), (b) are the contents of the knowledge base for KPTDocument and KPTAction respectively. Fig. 22 shows an example content of the knowledge base, (a), (b) are the contents of the knowledge base for KPTPerson and KPTContent respectively. Fig. 23 shows an example content of the Domain knowledge base. Fig. 24 shows an example User Interface of one embodiment. The keywords obtained in step S612 - KPT, Yokohama are displayed in the UI as shown in step S618. Fig. 25 shows an example User Interface of Save UI displayed in step S707, when Save is selected in Fig. 24, to get the validity or the period of time for which the contents needs to be saved. Fig. 26 shows example results of the knowledge structures (a), (b) created in Step S612 and for KPTAction and KPTDocument respectively. Fig. 27 shows an example HTML text obtained from the browser. In step S621, the system obtains the HTML text like shown in this figure and in steps SI 604 to. SI 608, downloads the embedded files, which happens to be image files with '.gif extension for the example HTML file shown. Fig. 28 shows example results of the knowledge structures. These knowledge structures are created and updated to knowledge base in step SI 608 for the example HTML text shown in Fig. 27. Fig. 29 shows example modified HTML text. The original HTML text obtained from the browser, shown in Fig. 27 is modified by the system in step SI 606 and the resultant HTML text is shown in this figure. As can be seen from this figure, the embedded links are modified to reflect the path where the system stores the embedded contents. Fig. 30 shows example results of the knowledge structures created in step SI 506 of this embodiment. Fig. 31 shows an example User Interface of Hold UI, displayed in step S709, when Hold is selected in Fig. 24, to get the validity or the period of time for which the contents needs to be held by the system. Fig. 32 shows an example User Interface of the Annotation UI displayed in step S714, when Annotation is selected to annotate, edit the HTML text from within the browser, without opening a separate window or application for the same purpose. Fig. 33 shows example modified HTML text after user has performed annotations. The example shows the modified HTML text after adding notes directly on to the page in step S903. As can be seen from the figure, no special or custom tags are created, only standard HTML tags are added and hence, the contents of the annotations can be viewed using any standard browser. Fig. 34 shows an example User Interface of Send UI, displayed in step S711, when Send is selected in Fig. 24, to get the recipients - "To", "Cc", "Subject" etc... As can be seen from the figure, the annotated page in Fig. 33 can be sent to any recipient from within the browser and since no special or custom tags are added for annotations, the contents of the page can be viewed by the recipient using any standard browser Fig. 35 shows an example User Interface of Extract Data UI, displayed in step S717, when Extract is selected in Fig. 24, to allow the extraction of specified data. Fig. 36 shows example results of knowledge structures created in step S1412 to be updated to the knowledge base. Fig. 37 shows an example User Interface of Session UI. In step S1202, for each session the KPTAction is sorted by Time and the result is as shown in this figure. Also, as can be seen from the figure, being a Retrieved URL, the RetrieveUI message is obtained in step S617 and displayed in S618. Fig. 38 shows an example User Interface of Get All Links UI. In step SI 303, the links are sorted by Organization and the resultant UI is displayed in step S1304 as shown. As can be seen from the figure, if a content has subdomains (e.g., sales.saora.com) then it will appear in multiple places below each of the organization nodes, such as sales, saora, etc. Fig. 39 shows an example User Interface of Get All Links UI. In step SI 306, the links are sorted by Domains and the resultant UI displayed in step SI 304 as shown. Fig. 40 shows an example User Interface of Get All Links UI. In step SI 307, the links are sorted by Keywords and the resultant UI displayed in step SI 304 as shown. As can be seen from the figure, if a content has multiple keywords then it will appear in multiple places below each of the keyword nodes. Fig. 41 shows an example Retrieve or Find UI, which is displayed in step SI 108. Fig. 42 shows an example Properties or Attributes UI of an entry selected in Fig. 41. Fig. 43 shows an example Retrieve Extracted Data or Find UI, which is displayed in step SI 110. Fig. 44 shows an example Address book UI, which is displayed in step SI 112. Fig. 45 shows an example Properties or Attributes UI of an entry selected in Fig. 44. Figs. 46 to 50 show some examples of User Settings UI, displayed in step SI 114 of this embodiment. Fig. 51 is a flowchart of the procedural steps of S619 of this embodiment, in which a check is made to see if any system task needs to be executed. In step S5101, a check is made to determine if any system action exists, which needs to be executed. If no such action exists, the process is terminated and retums. If system action exists, system task Tl is created in step S5102. A check is made in step S5103 to determine if the system action is CheckExpired. If so, RemoveExpired is executed in step S5104 to remove the information whose validity period has expired. If not, a check is made in step S5105 to determine if the system action is CheckUpdate. If so, Update is executed in step S5016 to update the version of the system. After the completion of the above steps, knowledge base is updated in step S5107 and system task Tl is terminated in step S5108 and the process returns. Fig. 52 is a flowchart of the procedural steps of RemoveExpired S5104 of this embodiment. Referring to the figure, in step S5201, a valid or active KPTAction is fetched from the knowledge base. In step S5202, a check is made to determine if no KPTAction was found in the previous step. If so, the process terminates and retums. If not, a check is made in step S5203 to determine if the validity period of the KPTAction is defined. If not, the control goes back to step S5202 to fetch the next valid or active KPTAction from the knowledge base and the process continues. If so, a check is made in step S5204 to determine if the validity period of the KPTAction has expired. If not, the control goes back to step S5201 otherwise, a confirmation is made to the user or based on user settings without asking the user every time, to verify if the found action can be deleted, in step S5205. If so, in step S5206 the KPTAction and the associated KPTDocument is deleted from the knowledge base and in step S5207 the knowledge base is updated and the control goes back to step S5201 to fetch the next valid or active KPTAction from the knowledge base and the process continues till no more actions are found. Fig. 53 is a flowchart of the procedural steps of CheckUpdate S5106 of this embodiment. In step S5301, the current version of the system, VI is obtained. In step S5302 a check is made to determine if the version V2 can be obtained from the website. If not, the process terminates and retums. If so, a check is made to determine if version V2 is greater than VI. If not, the process terminates and returns. If so, a check is made in step S5304, to see if user confirmation is required, in which case after confirming from the user, the latest version is downloaded in step S5305 and the system updates itself in step S5306 and the process retums. Fig. 54 is a flowchart of the procedural steps of Sort by keywords S1307 of this embodiment. Initially in step S5401 the NodeList is set to NULL. In step S5402, the list of all keywords LI, is retrieved from the knowledge base. In step S5403, the next keyword Kl is fetched from the list of keywords LI. A check is made in step S5404 to determine if Kl exists. If so, a check is made in step S5406 to determine if it is a required keyword. If not, the control goes back to step S5403. If so, a check is made in step S5407 to determine if the keyword Kl already exists in the NodeList. If so, the control goes back to step S5403. If not, the keyword Kl is added at the appropriate place in the NodeList in step S5408 and control goes back to step S5403 to fetch the next keyword from the list. If Kl does not exist in step S5404, implying that all the keywords in the NodeList were processed and hence in step S5405, ShowTreeView (NodeList, Type) is executed with Type=Keyword, whose details are explained in Fig. 55 and the example results are shown in Fig. 40, wherein the keywords in the NodeList are displayed in the sorted order. Fig. 55 is a flowchart of the procedural steps of ShowTreeView S5405 of this embodiment. First in step S5501, a check is made to determine if Type is Keyword. If so, no keyword is added to the NodeList in step S5502. In step S5503, the list of nodes in the NodeList is displayed. In step S5504, the process waits for user operation or Action Act and in step S5505, a check is made to determine if the Act is End, in which case the process returns. If not, a check is made in step S5506 to determine if a Leaf was selected. If so ProcessLeafAction(Act, Node, Type) is executed in step S5507. If not, ProcessNodeAction(Act, Node, Type) is executed in step S5508 and the process retums to step S5504. Fig. 56 is a flowchart of the procedural steps of ProcessLeafAction(Act, Node, Type) of step S5507 of this embodiment. A check is made in step S5601, if the Act is Open. If so, all the child nodes and all the actions KPTAction and associated KPTDocument are fetched in step S5602, from the knowledge base for the selected node and added to the NodeList at appropriate places in step S5603 and continues to step S5609. If not, a check is made in step S5604, if the Act is Close. If so, all the child nodes below the selected node are closed or hidden in step S5605 and continues to step S5609. If not, a check is made to determine if the Act is Delete. If so, a confirmation is sought from the user, if required, in step S5607 and if delete is not to be performed, it continues to step S5609, else all the KPTAction and associated KPTDocument for all the child nodes below the selected node is deleted from the knowledge base in step S5608 and continues to step S5609. In step S5609, the knowledge base is updated based on the type of action performed and in step S5610 the user interface is updated to reflect the updates made in the knowledge base. If in step S5606, the action is not Delete, the process retums. Fig. 57 is a flowchart of the procedural steps of ProcessNode Action (Act, Node, Type) of step S5508 of this embodiment. A check is made in step S5701 to determine if the Act is Display (i.e., to display the contents of the stored page), if contents are stored, otherwise, the original page needs to be displayed. If so, KPTAction and associated KPTDocument are fetched from the knowledge base for the selected node and added to the NodeList at appropriate place in step S5702 and continues to step S5714. If not, a check is made in step S5703 to determine if the Act is Source (i.e., to display the contents of the original page). If so, the KPTAction and associated KPTDocument are fetched from the knowledge base for the selected node in step S5704 and fetches the contents of the page from the original location or URL in step S5705 and continues to step S5714. If not, a check is made to determine if the Act is Delete in step S5706. If so, a confirmation is sought from the user, if required, in step S5707 and if delete is not to be performed, it continues to step S5714, else in step S5708, the associated KPTAction and KPTDocument are deleted from the knowledge base and continues to step S5714. If not, a check is made in step S5709 to determine if the Act is Delete from this group. If so, a confirmation is sought from the user, if required, in step S5710 and if delete is not to be performed, it continues to step S5714, else in step S5711, the associated attributes or properties of KPTAction and KPTDocument are modified in the knowledge base and continues to step S5714. If not, a check is made in step S5712 to determine if the Act is Show Property. If so, the associated properties or attributes of the KPTAction and KPTDocument for the associated node are fetched from the knowledge base in step S5713 and continues to step S5714. In step S5714, the knowledge base is updated based on the type of action performed and in step S5715 the user interface is updated to reflect the updates made in the knowledge base. If in step S5712, the action is not Show Property, the process returns. Fig. 58 is a flowchart of the procedural steps of Sort by Domain step S1306 of this embodiment. Initially the NodeList is set to NULL in step S5801. In step S5802, the entire top-level domain list LI is fetched from the knowledge base. In step S5803, the next domain name Kl in list LI is fetched. A check is made in step S5804 to determine if the domain name Kl exists. If so, a check is made in step S5806 to determine if the domain name Kl is unnecessary or not required domain. If so, it continues to step S5803 to fetch the next domain name from the list. If not, a check is made in step S5807 to determine if the Kl is already present in LI, if so, it continues to step S5803 otherwise the domain name Kl is added to the NodeList at the appropriate place in step S5808 and then continues to step S5803. In step S5804, if Kl does not exist, implying that all the items in the list LI have been processed, Fig. 55 ShowTreeView(NodeList, Type), with Type = Domain is executed in step S5805 and the example results are shown in Fig. 39, wherein the Domains in the NodeList are displayed in the sorted order. Fig. 59 is a flowchart of the procedural steps of Sort by Organization step S1303 of this embodiment. Initially the NodeList is set to NULL in step S5901. In step S5902, list of all the organizations LI are fetched from the knowledge base. In step S5903, the next organization name Kl in list LI is fetched. A check is made in step S5904 to determine if the organization name Kl exists. If so, a check is made in step S5906 to determine if the organization name Kl is unnecessary or not required entry. If so, it continues to step S5903 to fetch the next organization name from the list. If not, a check is made in step S5907 to determine if the Kl is already present in LI. If so, it continues to step S5903 otherwise the organization name Kl is added to the NodeList at the appropriate place in step S5908 and then continues to step S5903. In step S5904, if Kl does not exist, implying that all the items in the list LI have been processed, Fig. 55 ShowTreeView(NodeList, Type), with Type = Orgn is executed in step S5905 and the example results are shown in Fig. 38, wherein the Organizations in the NodeList are displayed in the sorted order. Fig. 60 is a flowchart of the procedural steps of For Each Session, Sort KPTAction by Time, step S1202 of this embodiment. Initially, in step S6001, the CurrD is set to GetCurrentDate(), which the current date of the system. In step S6002, the MinD is set to GetMinimumDate(), which the minimum or earliest date for which information exists in the knowledge base. In step S6003, the NodeList is set to NULL. In step S6004, GetPreviousYearNodes(NodeList, CurrD, MinD) as detailed in Fig. 61 is executed. In step S6005, GetBeforeCurrMonthNodes(NodeList, CurrD) as detailed in Fig. 62 is executed. In step S6006, GetBeforeCurrWeekNodes (NodeList, CurrD) as detailed in Fig. 63 is executed. In step S6007, GetCurrWeekNodes(NodeList, CurrD) as detailed in Fig. 64 is executed. In step S6008, ShowTreeView(NodeList, Type) with Type = Session is executed as detailed in Fig. 55 and the example results are shown in Fig. 37, wherein the Sessions in the NodeList are displayed in sorted order. Fig. 61 is a flowchart of the procedural steps of GetPreviousYearNodes (NodeList, CurrD, MinD) of step S6004 of this embodiment. A check is made in step S6101 to determine if Year(CurrD) > Year(MinD) (i.e., the year part of CurrD is greater than the year part of MinD). If not, the process retums. If so, Iyear is set to Year(MinD) (i.e., year part of MinD) in step S6102. In step S6103, a check is made to determine if Iyear < Year(CurrD) (i.e., Iyear is less than the year part of CurrD). If not, the process retums. If so, a check is made in step S6104 to determine if Iyear is equal to Year(CurrD) - 1. If so, a node called 'Last year' is created and added to the appropriate place in NodeList in step S6105. If not, nodes for that year (i.e., Iyear) is created (e.g., 1999 etc.) and added to appropriate place in NodeList in step S6106. In either case, the step S6107 is executed, wherein nodes are created only for 'Months' (e.g., January, June etc.) for which data exists for the specified Iyear in the knowledge base and added to appropriate places in NodeList. In step S6108, nodes are created only for 'Days' (e.g., 1, 3, 27 etc.) for each of the above 'Months' for which data exists in the knowledge base and are added to appropriate places in NodeList. In step S6109, Iyear is incremented and the process continues to step S6103, till Iyear becomes greater than or equal to year part of CurrD, at which point the process retums. Fig. 62 is a flowchart of the procedural steps of GefBeforeCurrMonthNodes (NodeList, CurrD) of step S6005 of this embodiment. Initially, in step S6201, hnonth is set to 1. A check is made in step S6202 to determine if Month(CurrD) (i.e., month part of CurrD) is equal to Imonth. If so, the process retums. If not, a check is made in step S6203 to determine if the values of Imonth and Month(CurrD)-l are equal. If so, step S6204 is executed in which, a node called 'Last month' is created and added to appropriate place in NodeList. If not, step S6205 is executed in which, the node with Month name (e.g., Jan or Jun etc.) is created and added to appropriate place in NodeList. In either case, after completion, step S6206 is executed, wherein nodes are created only for 'Days' (e.g., 1, 3, 27 etc.) for each of the above 'Months' for which data exists in the knowledge base and are added to appropriate places in NodeList. In step S6207, Imonth is incremented and the process continues to step S6202, till Imonth is equal to the month part of CurrD, at which point the process retums. Fig. 63 is a flowchart of the procedural steps of GetbeforeCurrWeekNodes (NodeList, CurrD) of step S6006 of this embodiment. Initially, in step S6301, Iweek is set to 1. A check is made in step S6302 to determine if Week(CurrD) (i.e., week part of CurrD) is equal to Iweek. If so the process returns. If not, a check is made in step S6303 to determine if the values of Iweek and Week(CurrD-l) are equal. If so, step S6304 is executed in which, anode called 'Last Week' is created and added to appropriate place in NodeList. If not, step S6305 is executed in which the node with Iweek is created (e.g., 1st week, 2nd week etc.) and added to appropriate place to NodeList. In either case after completion, step S6306 is executed, wherein nodes are created only for 'Days' (e.g., 1, 3, 27 etc.) for each of the above 'Weeks' for which data exists in the knowledge base and are added to appropriate places in NodeList. In step S6307, Iweek is incremented and the process continues to step S6302, till Iweek is equal to the week part of CurrD, at which point the process retums. Fig. 64 is a flowchart of the procedural steps of GetCurrWeekNodes (NodeList, CurrD) of step S6007 of this embodiment. Initially, in step S6401, Iday is set to StartofWeek(CurrD) (i.e., the starting day of the current week). A check is made in step S6402 to determine if Iday is greater than the Day(CurrD) (i.e., the day part of the CurrD). If so, the process retums. If not, in step S6403, a check is made to determine if Iday is equal to Day(CurrD)-l. If so, step S6404 is executed in which, a node called 'Yesterday' is created and added to appropriate place in NodeList and continues to step S6408. If not, step S6405 is executed in which, a check is made to determine if Iday is equal to Day(CurrD) (i.e., current day). If so, step S6406 is executed in which, a node called 'Today' is created and added to appropriate place in NodeList and continues to step S6408. If not, nodes are created only for 'Days' (e.g., 1, 3, 4 etc.) for which data exists in the knowledge base and added to appropriate places in NodeList and continues to step S6408. hi step S6408, child nodes are created for sessions of day(s) for which data exists in knowledge base and added to appropriate places to NodeList. Finally in step S6409, Iday is incremented by 1 and the process continues to step S6402, till Iday > Day(CurrD), at which point the process retums. Fig. 65 is a flowchart of the procedural steps of steps S1510, S1512 SaveFileContents() of this embodiment. A check is made in step S6501 to determine if the contents to be saved is SaveLink only. If so, the process continues to step S6506. In step S6502, a folder FI with the name based on the KPTDocument's name, which is a Globally unique identifier (GUID) is created, which ensures that the folder to be created is unique within and across the local system. In step S6503, a file called KPTIndex is created in the folder created in previous step. The actual page contents (i.e., HTML text) are saved to the file created in the previous step. The fully qualified file name (i.e., the folder name and the file name) is stored as the , physical URL location of the KPTDocument. In step S6506, FillKPTAction() is executed which is explained in detail in Fig. 66 and the other required indices are determined by referring to the knowledge base in step S6507 and the process returns. Fig. 66 is a flowchart of the procedural steps of S6506, FillKPTActionO of this embodiment. In step S6601, the contents of 'Keep As' are set to 'Remember As' field of KPTDocument. hi step S6602, the contents of 'URL' are set to 'LogicalURL' field of KPTDocument. In step S6603, the contents of 'keyword' are set to 'Keyword' field of KPTDocument. In step S6604, the time and date are set to 'WhenDone' field of KPTAction. hi step S6605, a check is made to determine if KPTAction is Save. If so, step S6606 is executed. If not, a check is made in step S6608 to determine if KPTAction is Hold. If so, in step S6606, the 'Validity' is set to 'WhenToDo' field of KPTAction and in step S6607, 'Page title' is set to 'Title' of KPTDocument and process returns. If not, step S6609 is executed, in which the 'WhenToDo' field of KPTAction is filled with value 'infinity' and the process retums. Thus, when the user selects Quick Save, this embodiment does not ask the user for file name or destination folder location and the actual process of saving the information be it page contents, annotated contents, page contents plus including all the links below them are stored in a one-touch operation. Also the same information be it a page or link can be stored multiple times (i.e., store the contents of the same link as many times as the user wishes), without ever specifying the filename, and still be able to retrieve them easily. This is especially useful, for users to keep track of the changes in the contents of the same web page. When user selects Save, user interface like Fig. 25 is shown to obtain optionally information regarding the validity or time period for which the contents needs to be saved. When user selects Hold, user interface like Fig. 31 is shown to obtain optionally information regarding the validity or time period for which the contents needs to be held on to. The Save option is basically for storing the information for long range of time, just like storing it in a file cabinet and Hold option for a short period, (i.e., for transient information), which is required to be for say a week or for a few days (e.g., Event or Show information, Limited Time Offers, etc.). The important part of setting the validity or time period for the information in this embodiment is that it will automatically be deleted, after the validity time expires, thus eliminating the time-consuming clean up operations. The user can, of course, keep the information forever, by specifying the validity as Indefinite. Also, if Automatic Save has been selected then all the information are automatically stored by this embodiment but for the URL(s) which are to be executed as specified by user in Fig. 50, are stored without any user intervention. Fig. 41 is an example for User Interface of Search UI, displayed in step SI 108. Fig. 67 is the flowchart for processing the retrieve conditions set in Fig. 41 and to fetch the appropriate information. In step S6701, Retrieve Query 'Q' is set to NULL. A check is made in step S6702 to determine if Keep As is NULL. If so, the input characters of keep As are set to Keep As of the Retrieve Query Q in step S6703 to retrieve the matching information starting with the given input and continues to step S6704. If not, a check is made in step S6704 is determine if keyword is NULL. If so, the input keyword is set to keyword of the Retrieve Query Q in step S6705 to retrieve the matching information and continues to step S6706. If not, a check is made in step S6706 to determine if Browse Date/ Validity Range is equal to NULL. If so, the input information is set to Browse Date/Validity Range of Retrieve Query Q in step S6707 and continues to step S6708. If not, a check is made in step S6708 to determine if Action Type is null. If so, the input Action Type is set to Action Type of query Q in step S6709 and continues to step S6710. If not, a check is made in step S6710 to determine if input URL is null. If so, the input characters of URL are set to URL of the retrieve query Q in step S6711 to retrieve query Q to retrieve the matching information starting the given input and continues to step S6712. If not, a check is made in step S6712 to determine if the input Page tile is NULL. If so, the input characters of Page title is set to Page Title of the retrieve query Q in step S6713 to retrieve query Q to retrieve the matching information starting the given input and continues to step S6714. If not, a check is made in step S6714 to determine if retrieve query Q is NULL (i.e., if any of the conditions to find was specified). If so, step S6715 is executed in which an error message is displayed to the user and continues to step S6702. If not, step S6716 is executed to retrieve all the matching KPTAction and associated KPTDocument from the knowledge base for the input retrieve query Q and the results are displayed to the user in step S6717 and the function retums. Fig.43 is an example for User Interface of Search Extracted Data UI for UI displayed in step SI 110. Fig. 68 is the flowchart for processing the retrieve conditions set in Fig.43 and to fetch the appropriate information. In step S6801, Retrieve Query "Q" is set to NULL. A check is made in step S6802 to determine if Keep As is NULL. If so, the input characters of Keep As are set to Keep As of the Retrieve Query "Q" in step S6803 to retrieve the matching information starting with the given input and continues to step S6804. If not, a check is made in step S6804 is determine if Name is NULL. If so, the input Name is set to name of the Retrieve Query "Q" in step S6805 to retrieve the matching information and continues to step S6806. If not, a check is made in step S6806 to determine if Extracted date is NULL. If so, the input information is set to Extracted date of Retrieve Query "Q" in step S6807 and continues to step S6808. If not, a check is made in step S6808 to determine if Retrieve Query "Q" is NULL (i.e., if any of the conditions to find was specified). If so, step S6809 is executed in which an error message is displayed to the user and continues to step S6802. If not, step S6810 is executed to retrieve all the matching KPTAction and associated KPTPerson from the knowledge base for the input retrieve query Q and the results are displayed to the user in step S6811 and the function retums. Fig. 69 shows example rules for determining the organization indices for a URL. As can be seen from the figure, the parameter, protocol, obvious address, page information is first removed from the URL. By referring to the Domain Knowledge base, whose example is shown in Fig. 23, the domain part of the URL is removed. The remaining URL is then processed to obtain the Organization indices as shown. Fig. 70 shows example rules for determimng the domain indices for a URL. As can be seen from the figure, the parameter, protocol, obvious address, page information is first removed from the URL. By referring to the Domain Knowledge base, whose example is shown in Fig. 23, the domain part of the URL is obtained. Fig. 71 shows a Client-Server type implementation of this embodiment. The figure illustrates an example Client-Server type implementation of embodiment of Fig. 2. Multiple clients 401 have KPT Cl system 402, and communicate with Server 403. Server 403 is equipped with KPT SI System 404, knowledge base management 405 and Database 406. Server 403 can also communicate with other servers to access their information stored in database, via knowledge base management. Fig. 72 is a flowchart of the procedural steps of INITIALIZE processing step S401 of a client 401, when the embodiment is implemented as Client-Server type implementation. In step S7201, the client first connects to the server. In step S7202, a check is made to determine if connection was successful. If not, error message is displayed in step S7203 and the process retums false. Otherwise, in step S7204, User information is got and using the information thus obtained, the client logs in to knowledge base in step S7205. In step S7206 a check is made to determine if the login to the knowledge base was successful. If not, an error message is displayed in step S7207 and the process retums false. Otherwise, the knowledge base is updated in step S7208. In step S7209, UI of this embodiment is displayed, an example of which is shown in Fig. 25 is shown and the process retums true. Fig. 73 is a flowchart of the main procedural steps of server 403, when the embodiment is implemented as Client-Server type implementation. In step S7301, initialization steps are executed. In step S7302, main function processing saving etc. of this embodiment at the server side is performed. In step S7303, terminate or clean-up processing is executed. Fig. 74 is a flowchart of lNITIALIZE_SERVER procedure of step S7301 of this embodiment when implemented as Client-Server. In step S7401, Session is created. In step S7402 knowledge base is updated. In step S7403, service is started to accept requests from clients and the process retums. Fig. 75 is a flowchart of the procedural steps of MAIN- PROCESSOR_SERVER procedure of step S7302 of this embodiment when implemented as Client-Server. In step S7501, a check is made if ActL has any requests from any client. If so, the process proceeds to step S7504. If no, a check is made to determine if there is any user operation and ActL is set to UserAction(). If so, the process proceeds to step S7504. If not, a check is made to determine if there are any system tasks to be performed and ActL is set to SystemActionQ. If not, the process retums to step S7501. In step S7504, a check is made to determine if ActL is equal to End System. If so, all the current active tasks are terminated in step S7505 and the knowledge base is updated in step S7506 and the process retums. If not, in step S7507 Executes erverAct( ActL) is executed The ExecuteServerAct is similar to the ExecuteAction of Fig. 14 of this embodiment, the only difference being instead of executing the action completely at the client-end, only a request is made by the client and the actual process is executed at the server end. The knowledge base is updated in step S7508 and the process retums to step S7501. Fig. 76 is a flowchart of TERMINATE_SERVER procedure of step S7303 of this embodiment when implemented as Client-Server. In step S7601 a check is made to determine if there are any active client connections. If so, message is sent to the clients to disconnect from this server since it is shutting down, hi either case the process proceeds to step S7603, where all the active sessions are terminated and the knowledge base is updated in step S7604 and the process retums. Other exemplary configurations of the system are furthered described below. Fig. 77 shows a File Server type implementation of this embodiment. The figure illustrates an example File Server type implementation of embodiment of Fig. 2. Multiple clients 501 have KPT C2 System 502, Knowledge Base Management 503, and communicate with Server 504. Server 504 is equipped with Date Base 406. Server 504 can also communicate with other servers to access their information stored in the database. This File Server type implementation differs from the Client Server type implementation only to the fact that all the processing is done at the client side and only the database is stored on the server, thus allowing multiple clients to share the data stored on the server. The server side does not have any processing module, but for the database. Fig. 78 shows a Distributed Clients type implementation of this embodiment. The figure illustrates an example Distributed Clients type implementation of embodiment of Fig. 2. Multiple clients 601 have KPT C3 System 602, Knowledge Base Management 603, Database 604 and communicate with other clients to access their information stored in individual databases. The Distributed Clients implementation differs from the Client Server type implementation only to the fact that all the processing is done at the client side and each individual client is able to access data stored on other clients, thus allowing multiple clients to share the data stored across clients in an distributed environment. Fig. 79 shows another example of Client-Server type implementation of this embodiment. The figure illustrates another example Client-Server type implementation of embodiment of Fig. 2. Multiple clients 701 have KPT C4 system 702, Knowledge base Management 703 and Index DB and communicate with Server 403. Server 403 is equipped with KPT SI System 404, knowledge base management 405 and Database 406. Server 403 can also communicate with other servers to access their information stored in database, via knowledge base management. The client in this case has the indexes of the information in index DB of the information stored in the server to enable it to process and display the information in a very efficient way, since during retrieve or sorting the client does not need to connect and fetch the information from the server, thus speeding up the process considerably. Fig. 80 shows an example implementation of this embodiment in which the server acts as a proxy server and all the connections to the intemet are via the proxy server. By combining the KPT Server and Proxy server, the information browsing and fetch is speeded up to considerable extent, since the proxy server has an in-built cache. Fig. 81 shows an example web server based implementation of this embodiment in which the server is a Webserver with KPT SI System, Knowledge base management and DB. The clients 601 themselves are mere browsers. Thus, the entire processing of this embodiment is done at the server end and the clients only act as a means of displaying the information and getting information from the user. Fig. 82 shows an example mixed implementation in which the clients can communicate not only with server, as in a File Server implementation, but also to other clients, as in a Distributed Client implementation. As can be seen from the figure, numerous other combinations, like the client communicating with a web server based implementation, proxy server based implementation can also be implemented. Fig. 83 shows another example of implementation of this embodiment, in which the knowledge base management 804 at the server end, not only communicates with Database 406, but also to other extemal databases 806 and other extemal web information 805. Thus, the clients not only view the contents of the internet, but can also view the contents of a local database or local web information, along the same lines described in detail earlier in this embodiment. Fig. 84 shows another example of compounded implementation of this embodiment, in which the client 902 not only has knowledge base management 903, at the client end not only communicates with Database 904, but also to other extemal databases 906 and other local web information 905 on the client but also to other clients or servers explained earlier in this embodiment. Fig.85 displays an example of Show All links User Interface for Distributed client implementation of this embodiment. The left hand side displays the links sorted on the specified attribute (Travel, in this example) of the current users' information and information on other client for example as can be seen in this figure, Taro's kee<p>oint and Suzuki's kee<p>oint. The right hand side view shows the contents of the saved information selected by the user for viewing on the left-hand side. It is obvious from the figure that it is possible that in case of Client Server implementation, the left-hand side view can be based on multiple servers and clients. It is also possible that only selected or customized servers or clients can be specified or defined in the left hand side view and also allow other clients to refer only after obtaining the necessary authentication or permission required to access the information. Fig.86 displays an example of Show All links User Interface for Client Server implementation of this embodiment. The left-hand side displays the links sorted on the specified attribute (Sports, in this example) of the current users' information and information on other Server for example, KPT Server and Saora Server. The right hand side view shows the contents of the saved information selected by the user for viewing on the left-hand side. It is obvious from the figure that it is possible that in case of File Server implementation, the left-hand side view can be based on multiple servers and clients. Figs. 87 and 88 display other examples of Show all links User Interface for extemal Database implementation of this embodiment. The left hand side displays the links sorted in the specified attribute (Organization Chart, Designation in these examples respectively). The right hand side view shows the contents of the saved information selected by the user for viewing on the left-hand side. Fig. 89 displays an example of Session User Interface for extemal Database implementation of this embodiment. The left hand side displays the links sorted in the time or session order. The right hand side view shows the contents of the saved information selected by the user for viewing on the left-hand side. Fig. 90 displays another example of Show all links User Interface for local web information implementation of this embodiment. The left-hand side displays the links sorted in the specified attribute (Product DB, in this example). The right hand side view shows the contents of the saved information selected by the user for viewing on the left-hand side. Fig. 91 displays another example of Session User Interface for File System implementation of this embodiment. The left hand side displays the links sorted in the time or session order. The sessions as can be seen from the figure are defined as from start of the working day till the end , or say from start of the day till lunch break and after lunch break to end of the day etc. The right hand side view shows the contents of the information selected by the user for viewing on the left- hand side. Thus, as it becomes obvious from this figure that the human beings keep track of the actions performed based on time and session and the contents of the proposed embodiment can be applied to any invention to sort and present the actions of an entity in time sorted, session fashion. The present invention described above may be applied to a system constituted of a plurality of computers, or a specific computer within a system, the object of the present invention can also be achieved by supplying a storage medium storing program codes of software for implementing the function of the above embodiment to a system or an apparatus, and reading out and executing the program codes stored in the storage medium by a computer (or a CPU or MPU) of the system or apparatus. In this case, the program codes read out from the storage medium implement the function of the present invention, and the storage medium storing these program codes constitutes the invention. Also, besides the function of the above embodiment is implemented by executing the readout program codes by the computer, the present invention includes a case where an OS (Operating System) or the like running on the computer performs a part or the whole of actual processing in accordance with designations by the program codes and thereby implements the function of the above embodiment. Furthermore, the present invention also includes a case where, after the program codes read out from the storage medium are written in a memory of a function extension board inserted into the computer or of a function extension unit connected to the computer, a CPU or the like of the function extension board or function extension unit performs a part or the whole of actual processing in accordance with designations by the program codes and thereby implements the function of the above embodiment. It is to be understood that the above description is only representative of illustrative examples of embodiments and implementations. For the reader's convenience, the above description has focused on a representative sample of all possible embodiments, a sample that teaches the principles of the invention. Other embodiments may result from a different combination of portions of different embodiments. The description has not attempted to exhaustively enumerate all possible variations. It should be recognized that the method, system and apparatus for monitoring connectivity across disparate networks has many applications, and is not limited to the representative examples disclosed herein. Alternate embodiments may not have been presented for some of the specific portions of the invention. Some alternate embodiments may result from a different combination of described portions, or other un-described alternate embodiments may be available for a portion. This is not to be considered a disclaimer of those alternate embodiments, because many of those un-described embodiments are within the literal scope of the following claims, and others are equivalent. It is to be further understood that the tasks described in the following claims can be sequenced in many different orders to achieve the desired result. Thus, the scope of the present invention covers conventionally known variations and modifications to the system components and the method steps described herein, as would be known by those skilled in the art.

Claims: CLAIMS WHAT IS CLAIMED IS: 1. A data processing system, comprising: data acquisition means for acquiring data; determination means for determining whether user requests saving of the acquired data; indexing means for assigning a predetermined index to the data requested for saving, said index dynamically assigned to the data; and saving means for saving the requested data and the assigned index in a predetermined storage unit. 2. The system according to Claim 1, wherein said data acquisition means acquires data from a browser client, said browser client allowing browsing of data in an intemet. 3. The system according to Claim 1, wherein the predetermined storage is a database, and said system further comprising data retrieving means for retrieving data from the database based on a user-supplied index, said user-supplied index specified by a user. 4. The system according to Claim 1, further comprising: sorting means for sorting indices of the data in the storage unit; and display means for displaying a result of the sorting by said sorting means. 5. The system according to Claim 4, wherein said sorting means performs the sorting based on a plurality of types of indices. 6. The system according to Claim 4, further comprising: selecting means for selecting an index from the indices displayed on said display means; and retrieval means for retrieving data corresponding to the index selected by said selecting means from the database. 7. The system according to Claim 4, further comprising: deleting means for deleting at least one index from the indices displayed on said display means; and removal means for removing data corresponding to the index deleted by said deleting means from the database. 8. The system according to Claim 4, wherein at least one of the data has a plurality of values for an index, and said sorting means places the plurality of values at positions corresponding to respective values. 9. The system according to Claim 2, said saving means comprising: folder creation means for creating a new folder for newly browsed data; file name assigning means for assigning a predetermined name to the newly browsed data without intervention by a user; and file saving means for saving the newly browsed data in the new folder with the assigned file name. 10. The system according to Claim 9, wherein said folder creation means creates the new folder with a folder name created based on a predetermined rule. 11. The system according to Claim 10, wherein the folder name is a fixed name. 12. The system according to Claim 2, said saving means comprising: file name generation means for generating a unique file name for the newly browsed data without intervention by a user; and file saving means for saving the newly browsed data with adding the generated file name. 13. The system according to Claim 2, wherein said indexing means acquires a URL of the data from the browser as the index. 14. The system according to Claim 2, wherein said indexing means acquires at least one of a keyword or a title embedded in the data from the browser as the index. 15. The system according to Claim 14, wherein said indexing means displays the keyword or the title acquired from the browser. 14. The system according to Claim 1, wherein the index includes a time when the data is saved, said system further comprising: node creation means for creating nodes corresponding to groups classified on the basis of the timing of saving, said node creation means creates a hierarchical nodes by dividing a group corresponding to a period into a plurality of sub group each corresponding to a shorter period and creating a node corresponding to each of sub group; and node displaying means for displaying a plurality of nodes created by said node creation means in an order of saving. 15. The system according to Claim 14, wherein the data is on the network and each of the group corresponds to a session for the network. 16. The system according to Claim 14, wherein the data is file data and each of the group corresponds to a period from a start to an end of a file system. 17. The system according to Claim 14, wherein the data is file data and each of the group corresponds to an operation in a period for a file system. 18. The system according to Claim 13, further comprising word assigning means for assigning a word specified by a user as a further index to the data to be saved by said saving means. 19. The system according to Claim 1, wherein if an index assigned to the data to be saved has been assigned to other data, said saving means saves the data as a new data or updates the other data according to a setting by the user. 20. The system according to Claim 1, wherein if an index assigned to the data to be saved has been assigned to other data, said saving means inquires to the user whether the data is to be saved as a new data or an updated data. 21. The system according to Claim 1, wherein said saving means saves the data in correspondence with an effective period, and said system further comprising: comparing means for comparing the effective period with a current time at a predetermined timing; and removal means for removing data in correspondence with the effective period before the current time based upon the result of a comparison by said comparing means. 22. The system according to Claim 21, wherein the predetermined timing is a time when the system accepts no operations by a user. 23. The system according to Claim 21, wherein said removal means requests a user to confirm the removal of the data and removes the confirmed data. 24. The system according to Claim 21, wherein said removal means requests a user to confirm the removal of the data or removes the data without confirmation by the user in accordance with a setting by the user. 25. The system according to Claim 21 , wherein if the effective period is not specified by the user, said saving means saves the data in correspondence with a non-limited effective period. 26. The system according to Claim 2, wherein said saving means saves the browsed data in a first save mode and saves the URL in place of the browsed data in a second save mode. 27. The system according to Claim 2, wherein said saving means saves the browsed data with data linked thereto. 28. The system according to Claim 2, wherein said saving means always saves the browsed data without any instruction for each of the browsed data by the user. 29. The system according to Claim 28, wherein said saving means saves the browsed data when the browsing is operated to move to another URL. 30. The system according to Claim 28, wherein said saving means is controlled not to save the browsed data in a URL specified by the user in advance. 31. The system according to Claim 2, further comprising index extracting means for extracting as an index a specific data from a data train constituting address of the browsed data in the network on the basis of a predetermined rale. 32. The system according to Claim 31 , wherein the specific data is a domain name. 33. The system according to Claim 32, wherein the predetermined rale is a rule for eliminating a parameter, a protocol, an obvious address, and page data from the data train, and extracting a domain name from the rest of the data with referring to a knowledge base of domain names. 34. The system according to Claim 31, wherein the specific data is a name of organization. 35. The system according to Claim 34, wherein the predetermined rale is a rale for eliminating a parameter, a protocol, an obvious address, page data, and domain name from the data train, and determining the rest of the data as an organization name. 36. The system according to Claim 35, wherein the predetermined rale includes a rale for dividing the rest of the data into partial data with a predetermined symbol and determining each of the partial data as an organization name. 37. The system according to Claim 1, further comprising sending means for sending the acquired data or a specific part thereof to a destination. 38. The system according to Claim 37, wherein the specific part is a URL of the saved data. 39. The system according to Claim 37, wherein the specific part is the saved data except for an embedded image. 40. The system according to Claim 2, further comprising editing means for editing the browsed data. 41. The system according to Claim 40, wherein said editing means includes annotation means for adding an annotation to the browsed data. 42. The system according to Claim 41, wherein said annotation means adds an annotation in such a manner that the annotation is distinguishable from the browsed data. 43. The system according to Claim 40, wherein said editing means includes changing means for changing a display form of a designated portion in the browsed data. 44. The system according to Claim 2, further comprising: extraction means for extracting a predetermined type of data from the browsed data; and extracted data saving means for saving the extracted data in the database. 45. The system according to Claim 44, wherein said extraction means extracts data in a predetermined column in response to a copying operation of data from a specified portion of the browsed data to the predetermined column, and said extracted data saving means saves the extracted data with an attribute corresponding to the predetermined column. 46. The system according to Claim 44, wherein the predetermined type of data includes at least one of an organization name, a person name, an E-mail address, a telephone number, a Fax number, and a keyword appended to the data. 47. The system according to Claim 2, wherein if the data requested to be saved includes data in other URL, said saving means downloads the included data from the other URL. 48. The system according to Claim 47, wherein if the data in the other URL has been downloaded, said saving means dispenses with the downloading of the data. 49. The system according to Claim 2, further comprising mode selection means for selecting an automatic save mode, and in the automatic save mode, said determination means always determines the user requests to save the browsed data without instruction for each of the browsed data. 50. The system according to Claim 3, wherein said data acquisition means, said determination means, said indexing means, said saving means, and said database are equipped in a server apparatus, and said system further comprising at least one client apparatus connected to said server apparatus, each of said client apparatus transmits a user request to said server apparatus and receives a response to the user request from said server apparatus. 51. The system according to Claim 50, wherein said data acquisition means in said server apparatus acquires data in an intemet. 52. The system according to Claim 50, wherein said server apparatus further comprising: a local database; a web information storage device for storing web information acquires from an intemet: and administration means for administrating data in either of said database, said local database, and said web information storage device. 53. The system according to Claim 52, wherein at least one of said client apparatus further comprising: a client local database; a client web information storage device for storing web information acquires from an internet: and client administration means for administrating data in either of said database, said local database, and said web information storage device. 54. The system according to Claim 3, wherein said database is equipped in a server apparatus, and said data acquisition means, said determination means, said indexing means, and said saving means are equipped in at least one client apparatus connected to said server apparatus. 55. The system according to Claim 3, wherein said system includes a plurality of client apparatuses, and said data acquisition means, said determination means, said indexing means, said saving means, and said database are equipped in each of said client apparatuses, and each of said client apparatuses can access the database equipped in another client apparatus. 56. The system according to Claim 3, wherein said database is equipped in a server apparatus, and index database for storing the indices of said database is equipped in at least one client apparatus connected to said server apparatus. 57. The system according to Claim 3, wherein said data acquisition means, said determination means, said indexing means, said saving means, and said database are equipped in a server apparatus, said data acquisition means acquires data in an intemet, and said system further comprising at least one browser connected to said server apparatus, each of said browser browses web page in the intemet via said server apparatus and transmits a user action on the browses web page to said server apparatus. 58. A data processing method comprising: acquiring data; determining whether a user requests to save the acquired data; assigning a predetermined index to the data requested to save, without inputting any index; and saving the requested data with the assigned index in a predetermined storage unit. 59. A computer-executable program for controlling a computer to perform data processing, said program comprising codes for causing the computer to perform: a data acquisition step of acquiring data; a determination step of determining whether or not a user requests to save the acquired data; an indexing step of assigning a predetermined index to the data requested to save, without inputting any index; and a saving step of saving the requested data with the assigned index in a predetermined storage unit. 60. A data processing method comprising: acquiring data; receiving a user request to save the acquired data; assigning a predetermined index to the data requested for saving; and saving the requested data with the assigned index in a predetermined storage unit. 61. The method of claim 60, wherein said predetermined index is dynamically generated. 62. The method of claim 61 , wherein said predetermined storage unit is a database. 63. The method of claim 62, further comprising retrieving data from said database based on a user-supplied index. 64. The method of claim 62, further comprising: sorting indices of the data saved in the database; and displaying a result of said sorting indices on a display unit. 65. The method of claim 64, wherein said sorting is performed on a plurality of index types. 66. The method of claim 65, further comprising: selecting an index from the indices displayed; and retrieving data corresponding to the index selected from the database. 67. The method of claim 66, further comprising: deleting at least one index from the indices displayed on said display unit; and removing data corresponding to said deleted index from the database. 68. The method of claim 67, further comprising assigning a user- specified word as a second index for the data to be saved. 69. The method of claim 68, further comprising sending the acquired data to a predetermined destination. 70. The method of claim 68, further comprising sending a specific part of the acquired data to a predetermined destination. 71. The method of claim 60, wherein said data is acquired from a browser client, said browser client allowing browsing of data in an intemet. 72. The method of claim 71 , further comprising creating a new folder for newly browsed data in said storage unit. 73. The method of claim 72, further comprising assigning a predetermined file name to said newly browsed data. 74. The method of claim 73, further comprising saving said newly browsed data in said new folder with said predetermined file name. 75. The method of claim 74, further comprising editing the browsed data. 76. The method of claim 75, wherein said editing includes adding an annotation to the browsed data, said annotation is distinguishable from the browsed data. 77. The method of claim 71 , further comprising: extracting a predetermined type of data from the browsed data; and saving the extracted data in the storage unit.

Inventors: JEYACHANDRAN SURESH, JOSEPH PREM ANAND, SUDA ARUNA ROHRA, JEYACHANDRAN, SURESH, JOSEPH, PREM, ANAND, SUDA, ARUNA, ROHRA
Applicants: SAORA KABUSHIKI KAISHA
Application year: 2001
Main classification: G06F17
IPC codes: G06F17