System for sharing content tabs

TECHNICAL FIELD

[0001] This disclosure relates to sharing information among computer users, and, more particularly, to sharing content tabs among users of a computer system.

BACKGROUND

[0002] Present computer systems can provide voluminous amounts of information to users. The relative ease of serving information over the World Wide Web or using a web-type interface as a window into an information database fuels the development of electronic information dissemination systems. The amount of information that system users demand continues to grow, however. Therefore, a continuing need exists for optimizing the organization of the voluminous information so that it can best benefit the users.

[0003] A common way to present information to users is to have the users operate a browser window that shows a series of formatted pages of information. An improvement to forcing a user to proceed through a series of pages is the use of a tab metaphor, which is a navigational aid that provides a conceptual categorization of information. In this improvement, a series of tabs are placed in a display window as an interface to multiple documents. Selecting one of the tabs causes an associated page to appear in the display window. Just as in the physical world where writing on paper tabs of folders indicates the contents of papers kept within the particular folders, computer generated tabs are used to indicate the contents of a page displayed when the tab is selected.

[0004]FIG. 1 shows an example of an information window <b>10</b> that includes a series of tabs <b>15</b>. There are four tabs <b>15</b> shown in the window <b>10</b> of FIG. 1, but almost any number of tabs could be present. Each tab <b>15</b> includes a tab label portion <b>16</b> and an associated tab page portion <b>18</b>. One of the tabs <b>15</b> in the window <b>10</b> is selected at any given time. For instance, in FIG. 1, the tab labeled “Client” is selected. Selecting any of the tab labels <b>16</b> by, for instance, clicking it with a mouse, causes the window <b>10</b> to display the tab's associated tab page <b>18</b>, and the previously displayed tab page <b>18</b> is then covered by the new page. Typically, all of the tab labels <b>16</b> for the tabs <b>15</b> on the window are always viewable on the window <b>10</b>, which allows for their easy selection.

[0005] In some information systems, users are allowed to design content or customize different tab pages. For instance, some commercial news websites allow a user to individualize a page such that the user's local news and weather appear when the user connects to the news site. Once reason for allowing so much customization is that each user may have different preferences about what should be displayed on their pages so that they derive the most benefit possible from the page.

[0006] Oftentimes, however, customizing page views is difficult and time consuming, which can leave a user frustrated. Frustrated users who do not customize their views may stop visiting the site, thereby depriving them of the information they could otherwise receive.

[0007] Embodiments of the invention address these and other deficiencies in the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The description may be best understood by reading the disclosure with reference to the drawings, wherein:

[0009]FIG. 1 is a view of an information screen that includes tabs.

[0010]FIG. 2 is a functional block diagram of an information system that can be used to implement embodiments of the invention.

[0011]FIG. 3 is a view diagram including a tab sharing function according to embodiments of the invention.

[0012]FIG. 4 is a functional block diagram of an information system that can be used to implement embodiments of the invention.

[0013]FIG. 5 is an example view of a screen that can be displayed to a content tab owner to share a content tab with another user.

[0014]FIG. 6 is an example view of a document that can be presented to a user when a content tab is sent to the user.

[0015]FIG. 7 is an example flow diagram showing processes that can be used in embodiments of the invention.

[0016]FIG. 8 is an example flow diagram showing processes that can be used in other embodiments of the invention.

[0017]FIG. 9 is an example flow diagram showing processes that can be used in still other embodiments of the invention.

DETAILED DESCRIPTION

[0018]FIG. 2 is a functional block diagram of an information system <b>5</b>. A content server <b>30</b> stores information content that can be ultimately delivered to a user of the information system <b>5</b>. Some or all of the information content stored by the content server <b>30</b> may be stored in a storage repository <b>32</b>, which may or may not be separate from the content server <b>30</b> itself. The content server <b>30</b> can, of course, store any type of information for use by the users, such as text, data, static or moving images, audio data, templates, forms, etc.

[0019] The content server <b>30</b> is coupled to a portal control <b>40</b>, which can format the content stored on the content server for use by users of the information system <b>5</b>. The portal control <b>40</b> includes various functions useful in the operation of the system <b>5</b> such as, for example, an HTTP (Hypertext Transport Protocol) or “web” server that delivers HTML (Hypertext Markup Language) pages to users in response to user input, a JAVA application server (J2EE) that implements java code and scripts initiated by a user's machine, etc. The portal control <b>40</b> can be implemented by computer programs running on a computer system, for instance. Additionally coupled to the portal control <b>40</b> is a user profile storage facility <b>42</b>, which stores user preferences, pages, templates, forms, and other information, including the tabs <b>15</b> that each user has selected to appear on a personal user page.

[0020] Users A and B each have views <b>50</b> displayed on their machines (not shown) that are automatically brought up when the user connects to the portal control <b>40</b> and the content server <b>30</b> using a document viewer or browser. The browser could be running on a typical computer or workstation, e.g. The views <b>50</b> are similar to a “home page” on a typical World Wide Web system. An example view <b>50</b> is illustrated in FIG. 3. In the view <b>50</b> are a set of tabs <b>15</b> that have been customized for a particular user. A user can customize his or her view <b>50</b> in several ways, one of which is to design which tabs <b>15</b> will be present in the view, and what content that the page, portions <b>18</b> of the tabs will contain.

[0021] A set of tab management tools <b>54</b> are located on the view <b>50</b> of FIG. 3. Shown are tools that allow the user to add or delete content from the page portion <b>18</b> of a current tab <b>15</b>, change the layout of the page portion of the current tab, share the tab with another user, rename the tab label <b>16</b> portion, delete the tab entirely, and move the tab. Also an add-a-tab function tool <b>56</b> is presented as one of the tab labels <b>16</b> itself, to indicate that the added tab label will be located in its place. Of course other tools <b>54</b> could be present on the view <b>50</b>, or some views <b>50</b> may not include all of the tools listed above.

[0022] Some of the tools <b>54</b> are self-explanatory. For instance, adding deleting and renaming the tabs <b>15</b> allow the user to add, delete, and rename the tabs within their view <b>50</b>. The move tab tool <b>54</b> allows the user to move any of their already created tabs <b>15</b> to any position within a maximum of five tabs allowed within the view <b>50</b> of the information system <b>5</b>. For instance, the “myReports” tab <b>15</b> on the view <b>50</b> of FIG. 3 could be moved to the first tab position on the left, occupying the space where the “home” tab is currently situated. Of course, the limit on a maximum number of tabs <b>15</b> is up to the system designer, and not necessarily limited to five.

[0023] The change layout tool and the add/delete content tools allow the user to determine the way information shown on their tabs <b>15</b> is presented, and which information is included. For instance, the page portion <b>18</b> of the selected tab <b>15</b> (“home” in the view <b>50</b> of FIG. 3) includes four sub-windows <b>20</b> in a particular layout. The add/delete content tool allows the user to select which sub-windows <b>20</b> will be on each page portion <b>18</b> of each tab <b>15</b>. In a financial environment, such as the one the view <b>50</b> of FIG. 3 is in, common sub-windows <b>20</b> that may be placed on a home tab <b>15</b> include: “Portal Help”, “Internet Development Info”, “Exchange Rate Calculator” and “Person Search”. On a news tab <b>15</b> might be found: competitor information, marketing information, and finance specific news. A directory tab <b>15</b> may include User lookups and lists of popular financial sites. One tab <b>15</b> may be named my reports, and various reports are viewed or printed from there. A tool tab <b>15</b> may include exchange rates calculator or a user lookup. A discussion tab <b>15</b> may include a link to various discussion forums, where users can read and post topics on discussion groups. Of course, the types of content available to be selected and have its layout customized by the users will vary depending on the underlying information system <b>5</b>. Embodiments of the invention are not limited to such specifics as described above, but can be applied to any conforming information system.

[0024] When a user is added to the information system <b>5</b>, they are assigned a default view <b>50</b>, which may or may not include pre-formatted tabs <b>15</b>. Each user is then allowed to design their own information tabs <b>15</b> by using the add tab tool <b>56</b> and the content and layout tools. Tabs <b>15</b> can be thought of as templates, where each template has a particular associated layout and particular content selected to fill that layout. The template in turn points to data stored on the content server <b>30</b>. In some embodiments, the template can be formatted by objects, as is known in the art.

[0025] Embodiments of the invention allow a user to use another of the tab tools <b>54</b>, “share a tab”, to transfer a particular tab to a second user so that the second user can also use the first user's tab in the second user's view <b>50</b>. Sharing tabs allows information created for a first user to be used by the second user, without requiring the second user to re-create the information that the first user already created.

[0026] One system that can be used to transfer a tab <b>15</b> from one user to another is illustrated in FIG. 4. In that figure, the portal control <b>40</b> includes interface applications or APIs <b>44</b> that interface between the portal control, the user profile storage <b>42</b>, and users of the information system <b>5</b>. The share a tab tool <b>54</b> is initiated by a user A selecting the share tab tool on user A's view <b>50</b> such as that shown in FIG. 3. The particular tab <b>15</b> that will be shared is the current tab selected on user A's view <b>50</b>. Selecting the share tab tool <b>54</b> signals a “package tab” or some similar function of the portal interface APIs <b>44</b> to copy the structure of the selected tab <b>15</b>. Copying the structure of the tab <b>15</b> can be performed by copying the template for the tab <b>15</b>, or by extracting objects and/or data from objects that make up or describe the template and placing them into an XML (Extensible Markup Language) string, for example. Such objects or data within the objects includes content of the tab <b>15</b>, the layout format of the tab, and the name of the tab. Of course, not all templates for the tabs <b>15</b> need include all of the data listed above, and other templates could include additional or different information.

[0027] A mailer process <b>46</b> can also be present within the portal control <b>40</b>, as is shown in FIG. 4. The mailer <b>46</b> can be JAVA based so that it can be easily integrated with the portal interface APIs <b>44</b>, for instance. Once the portal interface APIs <b>44</b> have packaged the selected tab <b>15</b> to be mailed in XML, the mailer <b>46</b> creates an HTML document containing the XML codes that were copied from the tab <b>15</b> and sends the HTML document to an email server <b>60</b>, specifically addressed to a user B, who is receiving the HTML document having the tab codes inside.

[0028]FIG. 5 shows an example screen <b>70</b> that appears for user A after user A selects the send a tab tool <b>54</b> from FIG. 3. The screen <b>70</b> is used to initiate a request that the tab <b>15</b> be sent to the user B. On screen <b>70</b>, an input box <b>72</b> allows the tab owner (user A) to search for a correct email address of an intended recipient of the tab to be sent. Search results are presented in a textbox <b>74</b>. Or, the user A may already know the intended recipient's address and simply enter the known email address in an input box <b>76</b>. Comments can be added in a text input box <b>78</b>, which will be presented to the user as described below. To cause the tab <b>15</b> to be copied and the email containing the tab to be sent to the desired user as described above, the user A selects a “send” button <b>79</b>.

[0029] Returning back to FIG. 4, the packaged tab <b>15</b> sits in the HTML formatted email on the email server <b>60</b> waiting to be “read” by user B. User B reads the email by connecting to the email server <b>60</b> and downloading an email message containing the codes of the tab <b>15</b>. By viewing the email containing the HTML codes, user B can decide if he or she wants to download the tab <b>15</b> into their own view <b>50</b> or if he or she wants to delete the email and not incorporate the tab.

[0030]FIG. 6 shows an example HTML formatted email message <b>80</b> that can be downloaded by user B from the email server <b>60</b>. The email <b>80</b> gives information about the share-a-tab process, and instructs the user B how to accept the tab <b>15</b> from user A. Additionally, any comments entered from user A in the text box <b>78</b> of FIG. 5 are shown. Although the coded tab <b>15</b> information is contained within the email <b>80</b>, much of the tab information itself is not displayed. User B can change the name of the tab <b>15</b> in a text box <b>82</b>, which is originally filled by the name that user A had called the tab. User B selects an “accept” button <b>84</b> to download the tab <b>15</b> into their personal view <b>50</b>.

[0031] If user B chooses to incorporate the tab <b>15</b> into their own view <b>50</b>, then he or she clicks on the accept button <b>82</b>. That action causes a browser window to open on User B's machine and sends an HTTP request to an unpackage or similar function in the portal interface APIs <b>44</b> of the portal control <b>40</b> (FIG. 4). After the tab <b>15</b> is unpacked, the portal interface API <b>44</b> validates the tab, and, if the tab is validated, stores the tab in the storage facility <b>42</b> as one of user B's tabs.

[0032] The portal interface API <b>44</b> performs several validations on the tab <b>15</b> prior to storing it as one of user B's tabs in the view <b>50</b>. For instance, the tab label <b>16</b> of the newly transferred tab <b>15</b> must be different than all of the other tab labels <b>16</b> of the tabs <b>15</b> already in user B's view. Additionally, because in the information system <b>5</b> there is a maximum of five tabs <b>15</b> available for each user, if the user already has five tabs, then the new tab cannot be validated. Finally, if user B enters a new tab name in the text box <b>82</b> of the tab email <b>80</b>, then the name must have no illegal characters and have a length equal to or shorter than a maximum. Other validations could be performed, of course

[0033]FIG. 7 lists example processes of embodiments of the invention used to effectuate a transfer of tab <b>15</b> to a user of an information system. A flow <b>100</b> begins at a process <b>105</b> where a tab transfer is initiated to be sent to a user. The user, to receive the tab, may initiate the process himself or herself, or a first user may select a particular tab to be transferred to another user.

[0034] After the particular tab <b>15</b> is determined that it will be sent to the user, data from the tab <b>15</b> is copied and perhaps packaged or extrapolated in a process <b>110</b>. One embodiment for carrying out this process would be, for instance, pulling out the necessary information objects and packing them using XML. Additionally this XML coding making up the structure of the tab could then be placed within an HTML document. Once the document is created in the process <b>110</b>, a process <b>115</b> sends it over to an email server <b>60</b> (FIG. 4). This can be performed in a number of ways. For instance, as described above, a JAVA process can be executed on the portal control <b>40</b> that generates the email and sends it to the email server <b>60</b>. Other mechanisms could also be used. After the process <b>115</b> sends the packaged tab email to the email server <b>60</b>, it can also generate a message to user A showing that the transfer was successful.

[0035] In a process <b>120</b>, user B connects to the email server <b>60</b> and retrieves the message (such as the formatted HTML message <b>80</b> of FIG. 6) that includes the coded tab <b>15</b>. An HTML displayer, typically found in email programs, is used to view the email message <b>80</b>. Then, once the receiving user B has decided that he or she will accept the tab <b>15</b>, they click on the accept button <b>84</b>, which is one implementation of a process <b>125</b> of FIG. 5 to have the tab inserted as one of user B's.

[0036] In process <b>130</b>, the tab <b>15</b> is unpacked and its contents are examined. Recall that in some examples a tab <b>15</b> includes content, layout and a name, and that, in information system <b>5</b>, each of the users has to individually subscribe to specific content for it to appear in their view <b>50</b>. Therefore, the process <b>130</b> automatically subscribes the user to the content that is in the newly transferred tab <b>15</b>. The process additionally unpacks the layout of the original tab as well.

[0037] In a process <b>135</b>, all of the tab verification processes discussed above are performed to ensure that user B can accept the tab. One such verification is that user B does not already have a tab <b>15</b> with the same name as the new tab. In some systems, not all users are able to subscribe to all types of content. For instance, managers may be able to generate lists of subordinates, while the subordinates have no such ability to generate lists of peers. In those cases, or others where specific content is governed by privileges or rights afforded the user, the process <b>135</b> will additionally check to ensure that the user B has the correct privileges to accept the tab <b>15</b>.

[0038] Finally, in process <b>140</b>, the new tab <b>15</b> is added to user B's user profile in the storage facility <b>42</b> of the information system <b>5</b>. A message can then be generated for user B to be displayed in the browser window on user B's machine that the tab sharing operation was successful, or, if there were errors, the message could inform what errors occurred. When user B subsequently connects to the content server <b>30</b> and the portal control <b>40</b>, the new tab will appear in user B's view <b>50</b>.

[0039]FIG. 8 is an example flow diagram used to explain another method that can be used to transfer a tab <b>15</b> from one user to another in an information system. Many of the processes in FIG. 8 overlap those of FIG. 7, and, for brevity, the overlapping processes will not be discussed with reference to FIG. 8.

[0040] In FIG. 8, a flow <b>150</b> also includes the process <b>105</b> repeated from FIG. 7, except that to implement that process, the user A, who originally has the tab <b>15</b> in his or her view <b>50</b>, initiates a transfer to user B, who doesn't have the tab. User A may click on the share-a-tab tool <b>54</b> on his or her view <b>50</b>, for instance. A process <b>155</b>, implemented by one of the portal interface APIs <b>44</b>, then generates a new “home” page for the user B, so that the next time the user B connects to the content server <b>30</b> and the portal control <b>40</b>, the user B sees an opportunity to download a new tab. The new “home” page for user B could be the same or a similar format of the email <b>80</b> shown in FIG. 6.

[0041] Clicking on the accept button <b>84</b> or another similar process performs the action of process <b>125</b> to initiate the tab sharing, similar to that in FIG. 7. The remaining processes <b>125</b>-<b>140</b> of the flow <b>150</b> of FIG. 8 are the same as in the flow <b>100</b> of FIG. 7, and the new tab <b>15</b> is delivered to the user B in the same manner. To implement the flow <b>150</b> of FIG. 8, there is no need for the email server <b>60</b> in the portion of the information system <b>5</b> illustrated in FIG. 4, so that could be eliminated.

[0042]FIG. 9 illustrates yet another example flow <b>160</b> used for sharing a tab <b>15</b> with a user of the information system <b>5</b>. In that flow, a process <b>165</b> is performed of presenting a list of possible tabs <b>15</b> to download into user's personal views <b>50</b>, such as by displaying a “download tab” web page viewable by all users of the information system <b>5</b>. The download page may be updated by other users as they create tabs they wish to make available to share. In this scenario, clicking on the share-a-tab tool <b>54</b> in their views <b>50</b> causes the currently selected tab <b>15</b> to be added to the “download tab” page. Or, managers of the information system <b>5</b> could generate their own tabs, and place them on the “download tab” page for users to add to their views <b>50</b>. Process <b>125</b> could then be implemented performed by users simply selecting a button from the “download tab” page to indicate a particular tab <b>15</b> is to be added to the view <b>50</b>, and the remaining processes <b>130</b>-<b>140</b> would add the tab to the user's view, as was performed in flow <b>100</b> of FIG. 7.

[0043] Having a system by which users can easily acquire content tabs that others have created can greatly reduce the amount of time, energy and resources spent in creating the tabs themselves. Having such a process to easily customize content tabs increases the chances that users of such information systems will derive useful benefit from the systems, and will find the systems easy and intuitive to use.

[0044] Although “tabs” are the vehicle for sharing content in an information system above described, nothing limits embodiments of the invention from appearing differently than they do in the above figures. For instance, the same “tabs” as described herein can appear in other forms, such as a “drop-down” list, select list or other menu type systems.

[0045] Implementation of the tab sharing system is straightforward and intuitive once the details of the invention as described above are known. As always, implementation of the invention is left to the system designer. The methods, procedures and functions used to describe embodiments of the invention do not form the invention itself, but are rather used to implement the invention. The methods, procedures, and functions presented herein are not necessary inherently associated with any particular computer or other apparatus. Rather, various general-purpose machines may be used with computer programs in accordance with the teachings herein, or it may prove more convenient to construct more specialized apparatus.

[0046] Thus, although particular embodiments for a tab sharing system in an information system have been discussed, it is not intended that such specific references be considered as limitations upon the scope of this invention, but rather the scope is determined by the following claims and their equivalents.