Summarizing portlet usage in a portal page
First Claim
1. A system for creating a portal page summarizing previous portal page usage comprising:
- a portal status recorder comprising a processor connected to a memory and operative to monitor detected usage of at least one instance of at least one portlet application within at least one portal page separately at each of a plurality of different times, wherein the detected usage comprises user selection of a particular data option from among a plurality of data options within at least one instance of the at least one portlet application, wherein selection of each of the plurality of data options directs a request to a server for separate types of dynamic data;
the portal status recorder operative to store the detected usage comprising the particular selection of the at least one data option and to record dynamically generated HTML fragments based on the dynamic data accessed for the at least one data option;
a summary portal generator, responsive to a trigger to create a summary portal page, operative to dynamically create a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times by;
accessing stored detected usage of the at least one instance of the at least one portlet at least one of the plurality of different times, wherein the stored detected usage comprises the particular data option selected from among a plurality of data options within the at least one instance of the at least one portlet application and comprises the previously generated dynamically generated HTML fragments for the at least one instance;
accessing current data for the particular data option for the at least one portlet application from dynamic data maintained by the server;
dynamically generating content for display within the separate instance of the at least one portlet application from the current data; and
specifying the separate instance of the at least one portlet application to display the dynamically generated content based on the current data and the previously generated dynamically generated HTML fragments, wherein the summary portal page provides a summary of at least a selection of a previous usage of the at least one portal page comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page.
1 Assignment
0 Petitions
Accused Products
Abstract
A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. Responsive to a trigger to generate a summary portal page, the portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of at least a selection of previous usage of the at least one portal page. The trigger to generate a summary portal page includes a user selecting which previous stored portal usage, including usage of individual portlet applications, to summarize in the summary portal page, such that the summary portal page renders a summary of only that content selected by the user.
-
Citations
19 Claims
-
1. A system for creating a portal page summarizing previous portal page usage comprising:
-
a portal status recorder comprising a processor connected to a memory and operative to monitor detected usage of at least one instance of at least one portlet application within at least one portal page separately at each of a plurality of different times, wherein the detected usage comprises user selection of a particular data option from among a plurality of data options within at least one instance of the at least one portlet application, wherein selection of each of the plurality of data options directs a request to a server for separate types of dynamic data; the portal status recorder operative to store the detected usage comprising the particular selection of the at least one data option and to record dynamically generated HTML fragments based on the dynamic data accessed for the at least one data option; a summary portal generator, responsive to a trigger to create a summary portal page, operative to dynamically create a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times by; accessing stored detected usage of the at least one instance of the at least one portlet at least one of the plurality of different times, wherein the stored detected usage comprises the particular data option selected from among a plurality of data options within the at least one instance of the at least one portlet application and comprises the previously generated dynamically generated HTML fragments for the at least one instance; accessing current data for the particular data option for the at least one portlet application from dynamic data maintained by the server; dynamically generating content for display within the separate instance of the at least one portlet application from the current data; and specifying the separate instance of the at least one portlet application to display the dynamically generated content based on the current data and the previously generated dynamically generated HTML fragments, wherein the summary portal page provides a summary of at least a selection of a previous usage of the at least one portal page comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method for creating a portal page summarizing previous portal page usage comprising:
-
monitoring detected usage of at least one instance of at least one portlet application within at least one portal page separately at each of a plurality of different times, wherein the detected usage comprises user selection of a particular data option from among a plurality of data options within at least one instance of the at least one portlet application, wherein selection of each of the plurality of data options directs a request to a server for separate types of dynamic data; storing the detected usage comprising the particular selection of the at least one data option and to record dynamically generated HTML fragments based on the dynamic data accessed for the at least one data option; responsive to a trigger to create a summary portal page, dynamically creating a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times by; accessing stored detected usage of the at least one instance of the at least one portlet at least one of the plurality of different times, wherein the stored detected usage comprises the particular data option selected from among a plurality of data options within the at least one instance of the at least one portlet application and comprises the previously generated dynamically generated HTML fragments for the at least one instance; accessing current data for the particular data option for the at least one portlet application from dynamic data maintained by the server; dynamically generating content for display within the separate instance of the at least one portlet application from the current data; and specifying the separate instance of the at least one portlet application to display the dynamically generated content based on the current data and the previously generated dynamically generated HTML fragments, such that the summary portal page provides a summary of at least a selection of a previous usage of the at least one portal page comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page. - View Dependent Claims (9, 10, 11, 12, 13, 14, 15)
-
-
16. A program product comprising a storage-type computer-usable device including a computer-readable program for creating a portal page summarizing previous portal page usage, wherein the computer-readable program when executed on a computer causes the computer to:
-
monitor detected usage of at least one instance of at least one portlet application within at least one portal page separately at each of a plurality of different times, wherein the detected usage comprises user selection of a particular data option from among a plurality of data options within at least one instance of the at least one portlet application, wherein selection of each of the plurality of data options directs a request to a server for separate types of dynamic data; store the detected usage comprising the particular selection of the at least one data option and to record dynamically generated HTML fragments based on the dynamic data accessed for the at least one data option; responsive to a trigger to create a summary portal page, dynamically create a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page by; accessing stored detected usage of the at least one instance of the at least one portlet at least one of the plurality of different times, wherein the stored detected usage comprises the particular data option selected from among a plurality of data options within the at least one instance of the at least one portlet application and comprises the previously generated dynamically generated HTML fragments for the at least one instance; accessing current data for the particular data option for the at least one portlet application from dynamic data maintained by the server; dynamically generating content for display within the separate instance of the at least one portlet application from the current data; and specifying the separate instance of the at least one portlet application to display the dynamically generated content based on the current data and the previously generated dynamically generated HTML fragments. - View Dependent Claims (17, 18, 19)
-
Specification