Patent 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 have the data stored in the database easily only by issuing an instruction to save without specifying any index.

Full Description:
CLAIM FOR PRIORITY  
       [0001]     This application claims priority from Application No. 2004-234682 filed on Aug. 11, 2004 in JAPAN.  
       FIELD  
       [0002]     A method and apparatus for processing data, and more particularly a method and apparatus for processing data browsed by an Internet browser.  
       BACKGROUND  
       [0003]     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.  
         [0004]     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.  
         [0005]     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  
       [0006]     According to certain embodiments of the present invention, the present invention provides a method and apparatus to save data, which a user wants to do with a simple operation.  
         [0007]     According to one of the embodiments, the present invention relates to a data processing method comprising the steps of acquiring data via an internet, selecting an attribute of data to be processed, extracting data of the selected attribute from an entire or a part of the acquired data, and performing a predetermined process on the extracted data.  
         [0008]     According to another embodiment, the present invention relates to a data processing method comprising the steps of displaying a web page acquired via an internet, displaying a menu of processes for data related to a link in the displayed web page in response to clicking a right button of a mouse on the web page, and performing a process selected by a user from the menu on the data related to the link.  
         [0009]     According to still another embodiment, the present invention relates to a data processing method comprising the steps of setting an index for data in advance of acquiring the data, displaying an identifier for the setting, acquiring data via an internet, and assigning, in response to selecting the identifier, the index corresponding to the identifier to an entire or a part of the acquired data and performing a predetermined process thereon.  
         [0010]     According to a further embodiment, the present invention relates to a data processing method comprising the steps of displaying a menu for selecting a process for data and specifying a URL, and obtaining data from the specified URL and displaying the obtained data.  
         [0011]     According to a further embodiment, the present invention relates to a data processing method comprising the steps of inputting a keyword, selecting a search engine for an internet search, and searching data by the selected search engine based on the input keyword.  
         [0012]     According to a further embodiment, the present invention relates to a data processing method comprising the steps of searching data, specifying a common attribute for a search result, and storing at least a part of the search result with the specified attribute.  
         [0013]     According to a further embodiment, the present invention relates to a data processing method comprising the steps of displaying at least one of a first menu for selecting an identifier name of a process and a second menu for a button image of a process, and switching one of the first and second menu currently displayed with another one.  
         [0014]     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 DRAWINGS  
       [0015]     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.  
         [0016]      FIG. 1  is a block diagram illustrating an exemplary hardware configuration according to an embodiment of the present invention.  
         [0017]      FIG. 2  shows the functional block diagram of an exemplary information processing system embodying the present invention.  
         [0018]      FIG. 3  shows an example of the system&#39;s small UI interface.  
         [0019]      FIG. 4  shows an example of the system&#39;s sessions UI interface.  
         [0020]      FIG. 5  shows an example of the system&#39;s links UI interface along with different sorting options.  
         [0021]      FIG. 6  shows an example of the system&#39;s links UI interface sorted by KeepAs.  
         [0022]      FIG. 7  shows an example of the system&#39;s main UI interface.  
         [0023]      FIG. 8  is a flowchart of exemplary procedural steps when a function key on the UI is pressed.  
         [0024]      FIG. 9  is a flowchart of exemplary procedural steps when the function key is associated to News.  
         [0025]      FIG. 10  is a flowchart of exemplary procedural steps when the function key is associated to Search Results.  
         [0026]      FIG. 11  is a flowchart of exemplary procedural steps when the function key is associated to News On Hold.  
         [0027]      FIG. 12  is a flowchart of exemplary procedural steps when the function key is associated to Web Search.  
         [0028]      FIG. 13  is a flowchart of exemplary procedural steps when the function key is associated to MyPage.  
         [0029]      FIG. 14  is a flowchart of exemplary procedural steps when the function key is associated to k-search.  
         [0030]      FIG. 15  is a flowchart of exemplary procedural steps when the function key is associated to MyDocuments.  
         [0031]      FIG. 16  shows an exemplary table for Function Key associations.  
         [0032]      FIG. 17  is a flowchart of exemplary procedural steps of the system flow for the custom function keys of small UI.  
         [0033]      FIG. 18  is a flowchart of exemplary procedural steps of UserSpecifications.  
         [0034]      FIG. 19  shows an exemplary table for the Dictionary of Functions.  
         [0035]      FIG. 20  shows an exemplary table for the Dictionary of Function Names.  
         [0036]      FIG. 21  shows an exemplary table for the Dictionary of KeepAs.  
         [0037]      FIG. 22  shows an exemplary table for the Dictionary of Keywords.  
         [0038]      FIG. 23  shows an exemplary table for the Dictionary of Icons  
         [0039]      FIG. 24  shows exemplary user settings for user defined save function key.  
         [0040]      FIG. 25  is a flowchart of exemplary procedural steps of the system flow for displaying the small UI.  
         [0041]      FIG. 26  is a flowchart of exemplary procedural steps of Save.  
         [0042]      FIG. 27  is a flowchart of exemplary procedural steps of GetHTMLData.  
         [0043]      FIG. 28  is a flowchart of exemplary procedural steps of GetTargetHTMLandSetSelectionFlag.  
         [0044]      FIG. 29  is a flowchart of exemplary procedural steps of FetchTopHtml.  
         [0045]      FIG. 30  is a flowchart of exemplary procedural steps of FetchImagesOnly.  
         [0046]      FIG. 31  is a flowchart of exemplary procedural steps of FetchLinks.  
         [0047]      FIG. 32  is a flowchart of exemplary procedural steps of ImportCheck.  
         [0048]      FIG. 33  is a flowchart of exemplary procedural steps of FetchAllEx2.  
         [0049]      FIG. 34  is a flowchart of exemplary procedural steps of FetchAll.  
         [0050]      FIG. 35  is a flowchart of exemplary procedural steps of DoTheLayout.  
         [0051]      FIG. 36  is a flowchart of exemplary procedural steps of system search from small UI.  
         [0052]      FIG. 37  shows an example of Synchronize Properties of search and organization.  
         [0053]      FIG. 38  shows an example of user settings for Save function.  
         [0054]      FIG. 39  shows an example of user settings for Go to URL function.  
         [0055]      FIGS. 40 and 41  are flowcharts of exemplary procedural steps for right click Save.  
         [0056]      FIG. 42  shows an exemplary result of QuickSave  
         [0057]      FIG. 43  shows an exemplary result of Advanced Save with Text Only SaveOption.  
         [0058]      FIG. 44  shows an exemplary result of Advanced Save with Images Only SaveOption.  
         [0059]      FIG. 45  shows an exemplary result of Advanced Save with Links Only SaveOption.  
         [0060]      FIG. 46  shows an example of area selection on HTML page.  
         [0061]      FIG. 47  shows an exemplary result of Quick Save for a selected area.  
         [0062]      FIG. 48  shows an exemplary result of Advanced Save with Text Only SaveOption for a selected area.  
         [0063]      FIG. 49  shows an exemplary result of Advanced Save with Images Only SaveOption for a selected area.  
         [0064]      FIG. 50  shows an exemplary result of Advanced Save with Links Only SaveOption for a selected area.  
         [0065]      FIG. 51  shows an exemplary result of Quick Save with Page+ option.  
         [0066]      FIG. 52  shows an exemplary result of Advanced Save with Page+ Text Only SaveOption.  
         [0067]      FIG. 53  shows an exemplary result of Advanced Save with Page+ Images Only SaveOption.  
         [0068]      FIG. 54  shows an exemplary result of Advanced Save with Page+ Links Only SaveOption.  
         [0069]      FIG. 55  shows an exemplary database table for a saved page.  
         [0070]      FIG. 56  is a flowchart of exemplary procedural steps for GetSaveOption.  
         [0071]      FIG. 57  is a flowchart description of exemplary associated functions for various buttons on the main UI.  
         [0072]      FIG. 58  is a flowchart of exemplary procedural steps for the Main UI Save.  
         [0073]      FIG. 59  is a flowchart of exemplary procedural steps for the Automatic Save.  
         [0074]      FIG. 60  is a flowchart of exemplary procedural steps for Detailed Save.  
         [0075]      FIG. 61  is a flowchart of exemplary procedural steps for Export.  
         [0076]      FIG. 62  is a flowchart of exemplary procedural steps for Send.  
         [0077]      FIG. 63  is a flowchart of exemplary procedural steps for Save UserFlow.  
         [0078]      FIG. 64  is a flowchart of exemplary procedural steps for Save UI.  
         [0079]      FIG. 65  is a flowchart of exemplary procedural steps for Advanced Save UI.  
         [0080]      FIG. 66  is a flowchart of exemplary procedural steps for Save Page+ UI.  
         [0081]      FIG. 67  is a flowchart of exemplary procedural steps for KeepAs view user flow.  
         [0082]      FIG. 68  is a flowchart of exemplary procedural steps for getting the KeepAs view when a user clicks on keepoint R  from a browser toolbar or menu.  
         [0083]      FIG. 69  is a flowchart of exemplary procedural steps for getting the pages under KeepAs view when a user clicks on an action or a KeepAs or &lt;No KeepAs&gt;.  
         [0084]      FIG. 70  shows an exemplary result of Advanced Save with Page+ Links Links SaveOption.  
         [0085]      FIG. 71  is an example of Advanced save UI without area selection.  
         [0086]      FIG. 72  is an example of Advanced save UI with area selection.  
         [0087]      FIG. 73  is an example of right click anywhere on the page.  
         [0088]      FIG. 74  is an example of right click on links only.  
         [0089]      FIG. 75  is an example of right click on the selected area.  
         [0090]      FIG. 76  is an example of Top HTML Save with area selection.  
         [0091]      FIG. 77  is an example of Quick Save UI of Selected Area with layout.  
         [0092]      FIG. 78  is an example of Search and Organize UI.  
         [0093]      FIG. 79  is an example of assigning the value of KeepAs as one of the KeeTools. 
     
    
     DETAILED DESCRIPTION  
       [0094]     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.  
         [0095]      FIG. 1  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 .  
         [0096]     A RAM  102  is used to temporarily store variables and intermediate data generated during the processing. A program from an external 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.  
         [0097]     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)  106  stores data of a database, a program, and the like.  
         [0098]     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.  
         [0099]      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 .  
         [0100]      FIG. 3  displays the small UI of system invented on the internet explorer browser window.  
         [0101]      FIG. 4  gives an outlook of the internet explorer browser window giving information pertaining to the system sessions.  
         [0102]      FIG. 5  gives an outlook of the internet explorer browser window giving information pertaining to the system links along with the sorting options such as sorted by KeepAs, sorted by domains, sorted by keywords etc.  
         [0103]      FIG. 6  gives an outlook of the internet explorer browser window giving information pertaining to the system links when it is sorted by KeepAs.  
         [0104]      FIG. 7  displays the main UI of system on the internet explorer browser window.  
         [0105]      FIG. 8  is a flowchart of an exemplary system flow when the user presses a function key on the UI. In step S 0801 , a check is made to determine if the pressed function key is Toggle or not. If it is Toggle, then in step S 0803 , the DisplayMainUI function is called. If not, then in step S 0802 , a check is made to determine whether an area is selected on the HTML page or not. If an area is not selected, then in step S 0804 , the selection is set to N. In step S 0805 , a check is made to determine whether the function key pressed is Search or not.  
         [0106]     If Search is pressed, then a check is made in step S 0806 , to determine if the search edit box is empty or not. If it is empty, a check is made in step S 0808  to determine if the selection is set to Y or not. If not, then an error message is shown to the user in step S 0812 . If, however, the selection is set to Y, then words from selected area are fetched as search keywords in step S 0809 . In step S 0810 , parameters are fetched from the database.  
         [0107]     If, however, the search edit box is not empty, then in step S 0807 , words from search edit box are fetched as keyword search. This step is followed by step S 0810 .  
         [0108]     If the search function key is not pressed, then step S 0810  is followed.  
         [0109]     Following step S 0810 , function with parameters, search keywords and selection flags is called in step S 0811  and the process ends.  
         [0110]      FIG. 9  is a flowchart of exemplary procedural steps when the function key is associated to News. In step S 0901 , values of KeepAs associated with the function key is fetched. If the value fetched is news, then in step S 0903 , KeepAs is set to news. However, if the value fetched is ebills, then in step S 0902 , the KeepAs is set to ebills. If any other value is fetched, then in step S 0904 , KeepAs is set to others. The save function is called in step S 0905  and the process ends.  
         [0111]      FIG. 10  is a flowchart of exemplary procedural steps when the Function key is associated to Search Results. In step S 1001 , KeepAs is set to Search Results. Then, the value of the search engine is fetched in step S 1002 . If the fetched search engine is A, then the keywords are fetched from search engine A in step S 1004 . Otherwise, if the fetched search engine is B, then in step S 1003 , the keywords are fetched from search engine B. In any other case, the keywords is set to null in step S 1005 . Then, in step S 1006 , keywords are set to the keywords found from search engines. In step S 1007 , Save function is called and the process ends.  
         [0112]      FIG. 11  is a flowchart of exemplary procedural steps when the Function key is associated to News On hold. In step S 1101 , expiry time is set to the given time. In step S 1102 , KeepAs is set to the given KeepAs. Then, in step S 1103 , the Save function is called and the process ends.  
         [0113]      FIG. 12  is a flowchart of exemplary procedural steps when the Function key is associated to Web Search. In step S 1201 , Search keywords are set to given words. Then, in step S 1202 , the search engine specified by the function key with the search keywords is called. The results are finally displayed in step S 1203  and the process ends.  
         [0114]      FIG. 13  is a flowchart of exemplary procedural steps when the Function key is associated to MyPage. In step S 1301 , URL is set to the given URL. In step S 1302 , a check is made to determine whether the page is to be opened in a new window or not. If it is to be opened in a new window, then in step S 1303 , a new HTML is opened. Finally, navigate to the given URL in step S 1304  and the process ends. However, if the page is not to be opened in a new window, then the process is simply directed to step S 1304 .  
         [0115]      FIG. 14  is a flowchart of exemplary procedural steps when the Function key is associated to k-search. In step S 1401 , search words are set to the given words. Then, in step S 1402 , system DB is searched for search words in keywords, KeepAs, domain name, organization name or full text. In step S 1403 , a check is made to determine if any entries are found or not.  
         [0116]     If any entries are found, then in step S 1404 , the results are displayed. Otherwise, in step S 1405 , the Nothing found flag is set to true. The system help file is then searched in step S 1406 . Again, in step S 1408 , a check is made to determine if any entries are found or not. If no entries are found, then an error message is displayed in step S 1410  and the process ends. If, however, any entries are found, then the results are displayed in step S 1407 , the Nothing found flag is set to false in step S 1409  and the process ends.  
         [0117]      FIG. 15  is a flowchart of exemplary procedural steps when the Function key is associated to MyDocuments. In step S 1501 , the Save Contents option is set to links only. In step S 1502 , KeepAs is set to the given KeepAs and Selection Flag is set to the given flag in step S 1503 . Then, in step S 1504 , the Save function is called and the process ends.  
         [0118]      FIG. 16  shows a table which gives an example content for Function Key associations with information pertaining to Function Key name, Function Id, Function Name, the various parameter values etc.  
         [0119]      FIG. 17  is a flowchart of exemplary procedural steps of the system flow for the custom function keys of small UI. In step S 1701 , the list of all possible functions is displayed to the user. In step S 1702 , the user is allowed to select a function or define a new function.  
         [0120]     In step S 1703 , the check is made to determine if the function is user defined or not. If it is not, then in step S 1704 , a check is made to determine if the function key is system defined or not. If not, then the UserSpecifications is called in step S 1705  for user to specify function parameters for a new function key or edit an existing one and the process ends. If the check in step S 1703  determines that the function is user defined, then step S 1705  is followed and the process ends.  
         [0121]     However if the function key is system defined then in step S 1706 , the user is allowed to edit the available function parameters, if any. Function parameters are search engine in case of Save Search Results, expiry time in case of On Hold Saves and search engine in case of Web Search. In step S 1707 , the specified parameters are stored in the database and then it goes back to step S 1702 .  
         [0122]      FIG. 18  is a flowchart of the procedural steps of UserSpecifications. In step S 1801 , user is allowed to associate an image with the function key. In step S 1802 , the function key associations are stored in the database. In step S 1803 , a check is made to determine if the user chose to add this function key to the UI. If not, then the process ends. If, however, the user chose to add the function key to the UI, then a check is made in step S 1804  to determine if the user has added the maximum number of function keys to the UI. If not, then in step S 1805 , the process goes to step S 1702  of  FIG. 17 . However, if the maximum number of function keys have been added to the UI, then in step S 1806 , the user is informed that he has added the maximum allowed function keys to the UI and the process ends.  
         [0123]      FIG. 19  shows a table which gives example content for the Dictionary of Functions with information regarding the User Id, Function Name, the various types of parameters along with their names etc.  
         [0124]      FIG. 20  shows a table which gives example content for the Dictionary of Function Names with information regarding the Function Name Ids and Function Names. The function names are either system defined or user defined.  
         [0125]      FIG. 21  shows a table which gives example content for the Dictionary of KeepAs with information regarding the KeepAs Id and the value of KeepAs.  
         [0126]      FIG. 22  shows a table which gives example content for the Dictionary of Keyword with information pertaining to the Keywords Id and the Keywords.  
         [0127]      FIG. 23  shows a table for the Dictionary of Icons. The table gives example content for the Dictionary of Icons with information pertaining to the Icon Id and the Images.  
         [0128]      FIG. 24  shows user settings for user defined save function key. The table gives an example of the User Settings for User Defined Save Function Key which gives information pertaining to the Function List, Function Names, KeepAs, Icons etc.  
         [0129]      FIG. 25  is a flowchart of an exemplary system flow for displaying the small UI. In step S 2501 , all the system defined fixed function keys are obtained. Then, in step S 2502 , all the user-defined function keys are obtained. In step S 2503 , space is assigned on the fixed toolbar. The system defined function key icons are then placed on the UI in step S 2504 .  
         [0130]     In step S 2505 , the available UI space is obtained depending on the system resolution. Finally, in step S 2506 , place as many user defined function key icons on the UI as can be placed in the available space and the process ends.  
         [0131]      FIG. 26  is a flowchart of exemplary procedural steps of SAVE. In step S 2601 , a check is made to determine if KeepAs is given or not. If it is given, then in step S 2602 , the KeepAs is set to given KeepAs. If not, then in step S 2603 , KeepAs is saved as null.  
         [0132]     In step S 2604 , a check is made to determine if keywords are given or not. If keywords are given, then keywords are set to given keywords in step S 2605 . If not, then in step S 2606 , keywords are fetched from the URL.  
         [0133]     In step S 2607 , a check is made to determine if the expiry time is given or not. If it is given, then in step S 2608 , the expiry time is set to the given expiry time. If not, then in step S 2609 , expiry time is set to infinity. In step S 2610 , a check is made to determine if the HTML data is given or not. If it is not given, then what is set to all and the selection is set to the whole page. In step S 2612 , GetHTMLData function is called. Then, in step S 2613 , data is saved with set indices to DB and the process ends. However, if the check in step S 2610  determines that the HTML data is given, then the step S 2613  is followed and the process ends.  
         [0134]      FIG. 27  is a flowchart of exemplary procedural steps of GetHTMLData function. In step S 2701 , GetTargetHTMLandSetSelectionFlag function is called. In step S 2702 , a check is made to determine the contents. If the content is Top HTML, then in step S 2703  FetchTopHTML function is called in step S 2703  and then DoTheLayout function is invoked and the process ends. If the content is Images Only, then in step S 2706  FetchlmagesOnly function is invoked and then DoTheLayout function is called and the process ends. If the content is All (with images), then in step S 2708  FetchAll function is called and then DoTheLayout function is invoked and the process ends. If the content is All (no ext. images), then in step S 2707  FetchAllEx2 function is called and then the DoTheLayout function is invoked and the process ends. If the content chosen is Links Only or Download Links, then in step S 2705  FetchLinks function is invoked. In step S 2709 , ImportCheck function is called and then DoTheLayout function is invoked and the process ends.  
         [0135]      FIG. 28  is a flowchart of exemplary procedural steps of GetTargetHTMLandSetSelectionFlag function. In step S 2801 , a check is made to determine if the user selected the Selected Area check box on the UI. If not, then in step S 2802 , selection is set to No and the html of the whole page is read in ‘HTML’ and the process ends. However, if the user selected the Selected Area check box on the UI, then a check is made in step S 2803  to determine if an area is actually selected on the HTML page. If selected, then in step S 2804  Selection is set to yes, pointers to the selected HTML are fetched, the selected HTML is read in HTML and the Html header is retained and the process ends.  
         [0136]     If an area is not selected on the HTML page, then in step S 2805 , the user is asked if he wants to select an area or select the whole page. If user selects an area, then the process goes back to step S 2803 . However, if the user decides to select the whole page, then the process goes back to step S 2802  and the process ends.  
         [0137]      FIG. 29  is a flowchart of exemplary procedural steps of FetchTopHTML function. In step S 2901 , Top Page is set to Y. In step S 2902 , the latest HTML is saved, but the resources are not saved. In step S 2903 , a check is made to determine the SaveOption. If the SaveOption is Page, then the process ends. However, if the SaveOption is Page+, then in step S 2904  a check is made to determine if the Top Page is set to Y or N. If it is set to Y, then in step S 2906  the first link is fetched and Top Page is set to N. In step S 2908 , the page for that link is fetched and the process goes to step S 2902 . If the check in step S 2904  determined that the Top Page was set to N, then in step S 2905  a check is made to determine if there are more pages to be fetched. If no, then the process ends. However, if more pages are to be fetched, then in step S 2907 , the next link is fetched and the process follows step S 2908 .  
         [0138]      FIG. 30  is a flowchart of exemplary procedural steps of FetchImagesOnly function. In step S 3001 , the top page is set to Y. In step S 3002 , the HTML header is retained and only image tags (and anchor tags if top page is set to Y) are kept from the HTML body. In step S 3003 , the final HTML is saved with images only and no resources are saved. Then, in step S 3004 , a check is made to determine the SaveOption. If it is Page, then the process ends. However, if it is Page+, then again a check is made in step S 3006  to determine the top page. If the top page is set to N, a check is made in step S 3005  to determine if there are more pages or not. If there are no more pages, the process ends. However, if there are more pages, the next link is obtained in step S 3007 , the page corresponding to that link is fetched in step S 3009  and the process is directed to step S 3002 .  
         [0139]     However, if the top page is set to Y in step S 3006 , then the first link is obtained and the top page is set to N in step S 3008  and the process is directed to step S 3002  through step S 3009 .  
         [0140]      FIG. 31  is a flowchart of exemplary procedural steps of FetchLinks function. In step S 3101 , the top page is set to Y. In step S 3102 , the HTML header is retained and only the anchor tags from the HTML body are kept. In step S 3103 , the final HTML is then saved with only the anchor tags. Then, in step S 3104 , a check is made to determine the SaveOption. If it is Page, then the process ends. However, if it is Page+, then again a check is made in step S 3105  to determine the top page. If the top page is set to N, a check is made to determine if there are more pages or not in step S 3106 . If there are no more pages, the process ends. However, if there are more pages, the next link is obtained in step S 3108 , the page corresponding to that link is fetched with all the resources in step S 3109  and the process is directed to step S 3104 .  
         [0141]     However, if the top page is set to Y in step S 3105 , then the first link is obtained and the top page is set to N in step S 3107  and the process is directed to step S 3104  through step S 3109 .  
         [0142]      FIG. 32  is a flowchart of exemplary procedural steps for Import Check. In step S 3201 , a check is made to determine if anything needs to be imported or not. If not, the process ends. Otherwise, the Save option is checked for Page or Page+ in step S 3202 . If it is Page, then in step S 3203  links are taken from the page, a separate save link is created for each in the import list and the process ends. However, if the Save option is Page+, then in step S 3204  a link is taken from the next page, the HTML data below that link is fetched in step S 3205  and a new page is created for this link in step S 3206  which is then added to the import list in step S 3207 . Finally in step S 3208 , a check is made whether there are more links or not. If not, the process ends. Otherwise, the process is directed to step S 3204 .  
         [0143]      FIG. 33  is a flowchart of exemplary procedural steps of FetchAllEx2 function. In step S 3301 , the top page is set to Y. In step S 3302 , the final HTML and all the resources except the external images are saved. In step S 3303 , a check is made to determine the SaveOption. If it is Page, then the process ends. However, if it is Page+, then again a check is made in step S 3304  to determine the top page. If the top page is set to N, a check is made to determine if there are more pages or not in step S 3306 . If no more pages are there, the process ends. However, if there are more pages, the next link is obtained in step S 3307 , the page corresponding to that link is fetched in step S 3308  and the process is directed to step S 3302 .  
         [0144]     However, if the top page is set to Y in step S 3304 , then the first link is obtained and the top page is set to N in step S 3305  and the process is directed to step S 3302  through step S 3308 .  
         [0145]      FIG. 34  is a flowchart of exemplary procedural steps of FetchAll function. In step S 3401 , TopPage is set to Y. In step S 3402 , the latest HTML and all the resources are saved. In step S 3403 , a check is made to determine the SaveOption. If the SaveOption is Page, then the process ends. However, if the SaveOption is Page+, then in step S 3404  a check is made to determine if the Top Page is set to Y or N. If it is set to Y, then in step S 3406  the first link is fetched and top page is set to N. In step S 3408 , the page for that link is fetched and the process goes to step S 2902  of  FIG. 29 . If the check in step S 3404  determined that the top page was set to N, then in step S 3405  a check is made to determine if there are more pages to be fetched. If no, then the process ends. However, if more pages are to be fetched, then in step S 3407  the next link is fetched and the process follows step S 3408 .  
         [0146]      FIG. 35  is a flowchart of exemplary procedural steps of DoTheLayout. In step S 3501 , the layout template is looked for. If it is user defined, then in step S 3502 , user is allowed to create a body template. If it is system defined, then in step S 3503 , standard body template is fetched. Then in step S 3504 , the template is applied to the input and the process ends.  
         [0147]      FIG. 36  is a flowchart of exemplary procedural steps for system search from small UI. The search keyword is entered in step  3601 , the search button is clicked in step S 3602  and then in step S 3603  the search results are displayed. The next action is then checked for in step S 3604 .  
         [0148]     If the next action to be performed is Advanced Search (step S 3605 ), then in step S 3606  the Advanced criteria is selected and the flow is directed to step S 3602 . If the next action to be performed is Next Search (step S 3609 ), then the process is directed to step S 3601 . If the next action to be performed is Synchronize properties (step S 3607 ), then go to  FIG. 37  in step S 3608  and the process ends if none of these are performed.  
         [0149]      FIG. 37  shows an example content displaying the synchronize properties available in the system. Synchronize properties contain information regarding the KeepAs, keywords and validity of the documents and appear in the search and organize browser window of the internet explorer.  
         [0150]      FIG. 38  gives an outlook of the browser window for the User Settings for the function Save. When this function is selected from the Function List, a list of folders appears under KeepAs and we can save our program under any of these.  
         [0151]      FIG. 39  gives an outlook of the browser window for the User Settings for the function Go To URL. When this function is selected from the Function List, a complete list of URLs appears and we can use any of the URLs depending on our requirement.  
         [0152]      FIGS. 40 and 41  are flowcharts of exemplary procedural steps for right click Save. In step S 4001 , the right click menu item clicked by the user is fetched. In step S 4002 , menu item clicked is checked. If it is Keep Page, then in step S 4004 , SaveOption is set to Page, and What is set to All (with images) and the process goes to Save. If the menu item clicked is Keep Page+, then in step S 4003 , SaveOption is set to Page+ and What is set to All (with images) and the process goes to save. If any other menu item is clicked, then in step S 4005 , process goes to  FIG. 41 .  
         [0153]     In step S 4101  of  FIG. 41 , menu item clicked is checked. If it is Keep Links Only, then in step S 4102  SaveOption is set to Page, What is set to Link Only, Import is set to No and the process goes to Save. If the menu item clicked is Import Links Only, then in step S 4103  SaveOption is set to Page, What is set to Link Only, Import is set to Yes and the process goes to Save. If the menu item clicked is Download and Import, then in step S 4104 , SaveOption is set to Page+, What is set to Download Links and Import is set to Yes and the process goes to Save. If the menu item clicked is Download and Keep, then in step S 4105  SaveOption is set to Page+, What is set to Download Links and Import is set to No and the process goes to Save.  
         [0154]      FIG. 42  shows exemplary results of Quick Save, i.e., the saved page when the Quick Save action has been performed.  
         [0155]      FIG. 43  shows an exemplary result of Advanced Save with Text Only save option. The page reflects the Text Only save option as only the text and no images have been saved throughout the page.  
         [0156]      FIG. 44  shows an exemplary result of Advanced Save with Images Only save option. The page reflects the ImagesOnly SaveOption as only the images and no text has been saved throughout the page.  
         [0157]      FIG. 45  shows an exemplary result of Advanced Save with Links Only save option. The page reflects the Links Only save option as nothing other than the links have been saved.  
         [0158]      FIG. 46  shows an example of area selection. The figure gives an outlook of how a page looks when a particular area is selected.  
         [0159]      FIG. 47  shows an exemplary result of Quick Save for the selected area. The figure simply displays the area that was selected.  
         [0160]      FIG. 48  shows an exemplary result of Advanced Save with Text Only save option for the selected area. The figure simply displays the area that was selected with only the texts and no images.  
         [0161]      FIG. 49  shows an exemplary result of Advanced Save with Images Only save option for the selected area. The figure displays only the images that correspond to the selected area.  
         [0162]      FIG. 50  shows an exemplary result of Advanced Save with Links Only save option for the selected area. The figure displays only the links that correspond to the selected area.  
         [0163]      FIG. 51  shows an exemplary result of Quick Save with Page+ option. The figure displays the entire page saved including the images and the links along with the pages associated with links of the saved page.  
         [0164]      FIG. 52  shows an exemplary result of Advanced Save with Page+ Text Only save option. The figure displays only the text of the page saved along with the pages associated with the links of the saved page. Sub-pages shown also contain only the text and no images.  
         [0165]      FIG. 53  shows an exemplary result of Advanced Save with Page+ Images Only save option. The figure displays only the images of the page saved along with the pages associated with the links of the saved page. Sub-pages shown also contain only the images and no text and links.  
         [0166]      FIG. 54  shows exemplary results of Advanced Save with Page+ Links Only save option. The figure displays only the links of the page saved along with the pages associated with the links of the saved page.  
         [0167]      FIG. 55  shows an exemplary database table for an exemplary saved page. The table gives information regarding the KeepAs keywords, document Id, action performed on those documents along with their date of implementation etc.  
         [0168]      FIG. 56  is a flowchart of exemplary procedural steps for GetSaveOption. In step S 5601 , save option selected by the user is fetched. If it is Page, then SaveOption is set to Page in step S 5603  and the process ends. If the save option is Page+, then in step S 5604  SaveOption is set to Page+ and the process ends. If the save option selected is Link, then in step S 5602  SaveOption is set to Link and the process ends.  
         [0169]      FIG. 57  is a flowchart describing exemplary actions performed when different keys are pressed by the user. In step S 5701 , a button is pressed by the user. In step S 5702 , a check is made to determine if the pressed button is Toggle or not. If it is Toggle, then in step S 5703  Display Small UI function is called; otherwise, in step S 5704 , a check is made to determine if the pressed button is Help or not. If it is Help, then in step S 5705  Help function is called; otherwise, in step S 5706 , a check is made to determine if the pressed button is web/k-search or not. If it is web/k-search, then in step S 5707  web search/k-search function is called; otherwise, in step S 5708 , a check is made to determine if the pressed button is Export/Send or not. If it is Export/Send, then in step S 5709  Export/Send function is called; otherwise, the Main UI Save function is called in step S 5710  and the process ends.  
         [0170]      FIG. 58  is a flowchart of exemplary procedural steps for the Main UI Save. In step S 5801 , the action performed by the user is fetched. In step S 5802 , a check is made to determine if the action performed by the user is Track or Autosave. If yes, then in step S 5804 , a check is made to determine if the action is Track. If it is Track, then in step S 5805  Save Option is set to Links Only. In step S 5809 , AutoSave is called and the process ends. If the Action is not Track, then in step S 5806  GetSaveOption function is called and then the process goes to step S 5809 .  
         [0171]     If the check in step S 5802  determined that the Action was not Track or Autosave, then in step S 5803  GetSaveOption function is called. In step S 5807 , a check is made to determine if the SaveOption is set to Link Only and the Action is QuickSave or not. If not, then SaveDetailed function is called in step S 5808  and the process ends. If, however, the SaveOption and Action are set to the requisite values, then in step S 5810  value of KeepAs is fetched from the edit box, keywords are fetched from the edit box, expiry time is set to infinity and title is set to page title. In step S 5811  Save function is called, and the process ends.  
         [0172]      FIG. 59  is a flowchart of exemplary procedural steps for Auto Save. In step S 5901 , a check is made to determine if the page is new or not. If the page is not new, the process ends. However, if the page is new, then URL is set from the browser in step S 5902 . The values of KeepAs, keywords and title are fetched and the expiry time is set to infinity in step S 5903 . Now in step S 5904 , a check is made to determine whether the save option is link or not. If it is link, then the link is saved in the DB in step S 5906 ; otherwise, FetchAll function is called in step S 5905  and then the link is saved in the DB in step S 5906  and the process ends.  
         [0173]      FIG. 60  is a flowchart of exemplary procedural steps for Detailed Save. In step S 6001 , a check is made to determine if the action is QSave or not. If it is QSave, then in step S 6003 , What is set to All. In step S 6004 , GetHTMLData is called. In step S 6006 , KeepAs is fetched from edit box and expiry time is set to infinity. In step S 6009 , SaveDB is called and the process ends.  
         [0174]     If the action is not QSave, then in step S 6002 , expiry time is obtained from the user. In step S 6005 , the value of What is obtained from the user and then in step S 6007  the HTMLData is called. In step S 6008 , KeepAs, keywords and page title are fetched from the edit box. It is followed by step S 6009  and the process ends.  
         [0175]      FIG. 61  is a flowchart of exemplary procedural steps for Export. In step S 6101 , the title is fetched and placed as filename, the current directory is fetched and placed as export path. In step S 6102 , the name specified for the exported file is fetched. In step S 6103 , the specified export path is fetched. In step S 6104 , the selected What option, viz. top HTML, Images Only, Links Only, All (no ext. images), All (with images) is fetched. In step S 6105 , SaveOption is set to Page and the GetHTMLData is called in step S 6106 . In step S 6107 , the data is exported and the process ends.  
         [0176]      FIG. 62  is a flowchart of exemplary procedural steps for Send. In step S 6201 , the title is fetched, formatted and put in the subject. In step S 6202 , the specified names of the email recipients (To and CC) are fetched. In step S 6203 , the specified subject is fetched. The specified note to be added to the email is fetched in step S 6204 . In step S 6205 , the selected What option, viz. Top HTML, Images Only, Links Only, All (no ext. images), All (with images) is fetched. In step S 6206 , the SaveOption is set to Page. In step S 6207 , GetHTMLData is called. In step S 6207 , data is exported and process ends.  
         [0177]      FIG. 63  is a flowchart of exemplary procedural steps for Save UserFlow. In step S 6301 , the user opens a browser window. In step S 6302 , user clicks on the keepointS icon on the toolbar to open the system Main UI in the browser window. In step S 6303 , as an optional step, the user selects a KeepAs from the existing list of KeepAs shown in combo box or specifies a new KeepAs. In step S 6304 , the user edits the keywords shown in the keywords edit box, adds new keywords or removes the existing ones. This step is also optional for the user. In step S 6305 , a check is made to determine if the user has selected an option from the radio buttons Link Only, Page or Page+. Then, in step S 6306 , a check is made to determine if the Track Check Box is checked or unchecked. If it is unchecked, the process takes the flow described in  FIG. 64 , as depicted in step S 6307 . If the box is checked, then the process ends. The result of this process is that all the links browsed in that Internet Explorer window will be automatically saved and visible as one session in the sessions view (step S 6308 ).  
         [0178]      FIG. 64  is a flowchart of exemplary procedural steps for Save UI. In step S 6401 , the user checks or unchecks the selected area check box. If it is checked, then if the user selects an area on the html page in step S 6402 , then he chooses either Quick Save or Advanced Save as the save option in step S 6404 . If Advanced Save is chosen, then the further procedure follows as in  FIG. 65 . However if Quick Save option is selected, then save operation is performed according to the Link, or Page or Page+ options specified by the user.  
         [0179]     If, however, the user does not select an area on the html page in step S 6402 , and he chooses the save option in step S 6405  (Quick Save or Advanced Save), then a message is displayed on the message box, as in step S 6406  asking the user if he wants to save the whole page or select an area. If the user decides to save the whole page, then the procedure from step S 6403  is followed. However, if he decides to select an area, then the procedure from step  6402  is followed.  
         [0180]     If the user unchecks the selected area check box, in the next step, step S 6403 , he chooses either Quick Save or Advanced Save as the save option. If Advanced Save is chosen, then the further procedure follows as in  FIG. 65 . However if Quick Save option is selected, then save operation is performed according to the Link, or Page or Page+ options specified by the user.  
         [0181]      FIG. 65  is a flowchart of exemplary procedural steps for Advanced Save UI. In step S 6501 , expiry time is selected. If the SaveOption is LinkOnly, then the result is as shown in  FIG. 45 .  
         [0182]     If Save option selected is Page, then in step S 6502  user selects an option from the What combo box. If Top HTML is selected, then result is as shown in  FIG. 48  if area has been selected, and as shown in  FIG. 43  if area has not been selected. If All (no ext images) option is selected from the What combo box, then if area has been selected, the contents of the selected area are saved excluding any external image within the selected area. However, if area has not been selected, then the contents of the whole page are saved excluding any external image. If Images Only option is selected from the What combo box, then the result is as shown in  FIG. 44  if area has been selected, and as shown in  FIG. 49  if area has not been selected. If Links Only option is selected from the What combo box, then result is as shown in  FIG. 50  if the area has been selected, and as shown in  FIG. 45  if area has not been selected. If All (with images) option is selected from the What combo box, then the result is as shown in  FIG. 47  if area has been selected, and as shown in  FIG. 42  if the area has not been selected.  
         [0183]     If the Save option selected is Page+, then the procedure follows as described in  FIG. 66 .  
         [0184]      FIG. 66  is a flowchart of exemplary procedural steps for Save Page+ UI. In step S 6601 , the user selects an option from the What combo box.  
         [0185]     If the option selected from the What combo box is Images Only, then the result is as shown in  FIG. 44  if area has been selected and as shown in  FIG. 49  if area has not been selected. If the option selected from the What combo box is Download Links, then the result is as shown in  FIG. 70  if area has been selected and as shown in  FIG. 54  if area has not been selected. If Top HTML option is selected, then the result is as shown in  FIG. 48  if area has been selected, and as shown in  FIG. 43  if area has not been selected. If All (no ext images) option is selected from the What combo box, then, if area has been selected, the selected area in the HTML page excluding any external images is saved, while if area has not been selected, then the entire HTML page is saved excluding any external images. If the option selected from the What combo box is All (with images), then the result is as shown in  FIG. 47  if area has been selected and as shown in  FIG. 42  if area has not been selected.  
         [0186]      FIG. 67  is a flowchart of exemplary procedural steps for KeepAs view user flow. In step S 6701 , the user opens an HTML page. In step S 6702 , user opens the system view by clicking on the keepointL icon on the browser window. In step S 6703 , user clicks on ‘Sorted By’ icon to choose KeepAs view. As a result, KeepAs view is now available, as depicted in step S 6704 .  
         [0187]      FIG. 68  is a flowchart of exemplary system flow procedural steps for getting the KeepAs view when user clicks on keepoint R  from browser toolbar or menu. In step S 6801 , the list of all the actions displayed in the view are fetched. In step S 6802 , the icons associated with the actions are fetched and added to the KeepAs view. In step S 6803 , a check is made to determine if the added action is Save action for the dated items. If not, then in step S 6805  all the KeepAs associated with special system defined functions, viz. Save Search Results, Put Items On Hold are added with the associated icons if any. In step S 6806 , all the other KeepAs not associated with any special functions are added. In step S 6807 , a &lt;No KeepAs &gt; is specified for pages or links for which a KeepAs was not specified and the process ends. If, however, the check in step S 6803  determined that the added action was not Save action for dated items, then in step S 6804  expiry time is added and sub-categories for validity such as 1 week, 1 month etc. are added and the process follows the procedure from step S 6805 .  
         [0188]      FIG. 69  is a flowchart of exemplary system flow procedural steps for getting the pages under KeepAs view when user clicks on an action or a KeepAs or &lt;No KeepAs&gt;. In step S 6901 , the node clicked by the user is identified as Action node, KeepAs node or &lt;No KeepAs node&gt;. If the node clicked is Action node, then in step S 6902 , a check is made to determine if the action node is a time sub-category under the dated items. If yes, then in step S 6904 , pages which have expiry in the specified time period are fetched and added and the process ends. If, however, the check in step S 6902  determined that action node is not a time sub-category under dated items, then in step S 6903 , pages are fetched and added under the specified action viz. Downloaded, Exported, Sent and Imported. In step S 6905 , pages having specified KeepAs are fetched and added and the process ends. If the node clicked is &lt;No KeepAs&gt;, then in step S 6906  the pages for which no KeepAs was specified by either the user or the system are fetched and added and the process ends.  
         [0189]      FIG. 70  shows an exemplary result of Advanced Save with Page+ Links SaveOption. The figure displays only the links of the page saved along with the links on the pages associated with the links of the saved page.  
         [0190]      FIG. 71  is an example of Advanced save UI without area selection.  
         [0191]     Here the actions performed by the Advanced Save option are in reference to the whole page. The entire page will be saved in such a case with the necessary specifications.  
         [0192]      FIG. 72  is an example of Advanced save UI with area selection. Here the actions performed by the Advanced SaveOption are in reference to the selected area. Only the selected area will be saved in such a case with the necessary specifications.  
         [0193]      FIG. 73  shows an example content of Right Click option anywhere on the page. Here the actions performed by the options of the Right Click are in reference to the entire page. The entire page will undergo a change in such a case.  
         [0194]      FIG. 74  shows an example content of Right Click option on the links only. Here the actions performed by the options of the Right Click are in reference to the links which are clicked or selected. Only the links will undergo a change in such a case.  
         [0195]      FIG. 75  shows an example content of Right Click option on the selected area. Here the actions performed by the options of the Right Click are in reference to the selected area. Only the selected portion will undergo a change in such a case.  
         [0196]      FIG. 76  is an example of Top HTML Save with area selection. It shows that with the Top HTML Advanced Save option, only the HTML text on the top page is saved excluding the images and links.  
         [0197]      FIG. 77  is an example of Quick Save UI of Selected Area with layout. It shows that the selected area on the HTML page is saved within the layout.  
         [0198]      FIG. 78  is an example of Search and Organize UI. It shows the result of a search action with specified search constraints. These search results can be organized using the synchronize button.  
         [0199]      FIG. 79  is an example of assigning the value of KeepAs as one of the KeeTools. It shows that with News on Hold as KeepAs, the QuickSave button is replaced by KeeTool. This implies that News on Hold has been assigned as a KeeTool.  
         [0200]     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 being 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.  
         [0201]     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.  
         [0202]     It is to be understood that the above description is only representative of illustrative examples of embodiments and implementations. For the reader&#39;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.  
         [0203]     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.  
         [0204]     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.

Technology Classification (CPC): 6