SUMMARIZING PORTLET USAGE CAPTURED RESPONSIVE TO TRIGGER EVENTS IN A PORTAL PAGE

• US 20110131501A1
• Filed: 01/04/2011
• Published: 06/02/2011
• Est. Priority Date: 10/15/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: LAURIDSEN, CHRISTINA K., WILCOX, LAUREN G., ONG, MALCOLM C.
• Granted Patent: US 8,615,711 B2
• Time in Patent Office: Days
• US Class Current: 715/738
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A portal summary controller monitors usage metadata indicating current usage of at least one portlet within at least one portal page for one of multiple events specified to trigger storage of the usage metadata. Responsive to detecting one of the multiple events within the usage metadata which triggers storage, the portal summary controller stores the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page. Subsequent to storing separate detected usage metadata at multiple different times, 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 multiple different times specified according to the separate usage metadata stored at each of the multiple different times, such that the summary portal page provides a summary of at least a selection of previous usage metadata selected by a user of the at least one portal page based on usage metadata stored responsive to trigger events.

Claims

1. A method for creating a portal page summarizing previous portal page usage comprising:

monitoring usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata;

responsive to detecting one of the plurality of events within the usage metadata, storing the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page;

subsequent to storing separate detected usage metadata at a plurality of different times, 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 separate usage metadata 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 metadata selected by a user of the at least one portal page;

presenting a graphical user interface for a user to select to save the summary portal page in association with one of a plurality of calendar events; and

responsive to a user selection of at least one particular calendar event from among said plurality of calendar events, storing a portlet specification of the summary portal page in association with the at least one particular calendar event.

2. The method according to claim 1, wherein monitoring usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata further comprises:

monitoring usage metadata for an event indicating that at least one of an additional portlet instance is added to the at least one portal page or an additional portal page is opened, wherein the event of an additional portlet instance added to the at least one portal page or an additional portal page opened is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the indicator that at least one of the additional portlet instance is added to the at least one portal page or the additional portal page is opened, triggering the storing of the detected usage metadata.

3. The method according to claim 1, wherein monitoring usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata further comprises:

monitoring usage metadata for an event indicating a user interaction with a particular portlet instance;

responsive to detecting the user interaction with a particular portlet instance, adjusting a graphical characteristic of the particular portlet instance to indicate the user interaction;

monitoring usage metadata for an event indicating adjustment of the graphical characteristic of the particular portlet instance, wherein adjusting a graphical characteristic of at least one portlet instance to indicate user interaction is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the event indicating adjustment of the graphical characteristic of the particular portlet instance, triggering the storing of the detected usage metadata.

4. The method according to claim 1, wherein monitoring usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata further comprises:

monitoring usage metadata for an event indicating that a particular portlet instance with a media viewer opens media within the media viewer, wherein the event of opening media with the media viewer is one of the plurality of events specified to trigger storage of the usage metadata;

responsive to detecting the event that the media viewer opens media within the media viewer, triggering the storing of the detected usage metadata, wherein the usage metadata comprises a timestamp of the play clock for the media within the media viewer;

monitoring subsequent usage metadata for a second event indicating that the particular portlet instance with the media viewer stops play of the media within the media viewer, wherein the event of stopping play of media within the media viewer is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the second event that the media viewer stops play of the media, triggering a second storing of the subsequent detected usage metadata at the time of the second event, wherein the subsequent detected usage metadata comprises a subsequent timestamp of the play clock for the media when play is stopped.

5. The method according to claim 1, wherein monitoring usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata further comprises:

monitoring usage metadata for an event indicating a user selection of a one of the selectable options among a plurality of selectable options within a particular portlet instance, wherein the event of a user selection of one of the selectable options within the particular portlet instance is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the event of the user selection of one of the selectable options within the particular portlet instance, triggering the storing of the detected usage metadata.

6. The method according to claim 1, further comprising:

storing usage metadata at the plurality of different times across a plurality of portal pages opened by a plurality of separate users; and

dynamically creating the 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 metadata stored at each of the plurality of different times for at least a selection of the plurality of separate users, such that the summary portal page comprises a summary of usage by the selection of the plurality of separate users.

7. The method according to claim 1, further comprising:

storing a file specifying the created summary portal page; and

providing an interface for a user to select to open the stored file for the summary portal page; and

responsive to the user selecting to open the stored file for the summary portal page, dynamically generating the summary portal page displaying the 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 metadata stored at each of the plurality of different times.

8. The method according to claim 1 wherein 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 separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of previous usage of the at least one portal page further comprises:

dynamically creating the summary portal page graphically distinguished from at least one other portal page and comprising a summary of said stored usage within at least one of a separate window and a tabbed window.

9. A system for creating a portal page comprising:

a portal status recorder comprising at least one processor and a memory configured to;

monitor usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata;

responsive to detecting one of the plurality of events within the usage metadata, store the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page;

a summary portal generator comprising the at least one processor and memory further configured to dynamically create a summary portal page from stored separated detected usage metadata at a plurality of different times 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 metadata stored at each of the plurality of different times;

a portal summary selection interface controller configured to present a graphical user interface for a user to select to save the summary portal page in association with one of a plurality of calendar events; and

responsive to a user selection of at least one particular calendar event from among said plurality of calendar events, the portal status recorder configured to store a portlet specification of the summary portal page in association with the at least one particular calendar event.

10. The system according to claim 9, the portal status recorder further configured to:

monitor usage metadata for an event indicating that at least one of an additional portlet instance is added to the at least one portal page or an additional portal page is opened, wherein the event of an additional portlet instance added to the at least one portal page or an additional portal page opened is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the indicator that at least one of the additional portlet instance is added to the at least one portal page or the additional portal page is opened, trigger the storing of the detected usage metadata.

11. The system according to claim 9, the portal status recorder further configured to:

monitor usage metadata for an event indicating a user interaction with a particular portlet instance;

responsive to detecting the user interaction with a particular portlet instance, for adjust a graphical characteristic of the particular portlet instance to indicate the user interaction;

monitor usage metadata for an event indicating adjustment of the graphical characteristic of the particular portlet instance, wherein adjusting a graphical characteristic of at least one portlet instance to indicate user interaction is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the event indicating adjustment of the graphical characteristic of the particular portlet instance, trigger the storing of the detected usage metadata.

12. The system according to claim 9, the portal status recorder further configured to:

monitor usage metadata for an event indicating that a particular portlet instance with a media viewer opens media within the media viewer, wherein the event of opening media with the media viewer is one of the plurality of events specified to trigger storage of the usage metadata;

responsive to detecting the event that the media viewer opens media within the media viewer, trigger the storing of the detected usage metadata, wherein the usage metadata comprises a timestamp of the play clock for the media within the media viewer;

monitor subsequent usage metadata for a second event indicating that the particular portlet instance with the media viewer stops play of the media within the media viewer, wherein the event of stopping play of media within the media viewer is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the second event that the media viewer stops play of the media, trigger a second storing of the subsequent detected usage metadata at the time of the second event, wherein the subsequent detected usage metadata comprises a subsequent timestamp of the play clock for the media when play is stopped.

13. The system according to claim 9, the portal status recorder further configured to:

monitor usage metadata for an event indicating a user selection of a one of the selectable options among a plurality of selectable options within a particular portlet instance, wherein the event of a user selection of one of the selectable options within the particular portlet instance is one of the plurality of events specified to trigger storage of the usage metadata; and

responsive to detecting the event of the user selection of one of the selectable options within the particular portlet instance, trigger the storing of the detected usage metadata.

14. The system according to claim 9, further comprising:

the portal status recorder configured to store usage metadata at the plurality of different times across a plurality of portal pages opened by a plurality of separate users; and

the summary portal generator configured to dynamically create the 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 metadata stored at each of the plurality of different times for at least a selection of the plurality of separate users, wherein the summary portal page comprises a summary of usage by the selection of the plurality of separate users.

15. The system according to claim 9, further comprising:

the portal summary recorder for storing a file specifying the created summary portal page; and

a portal summary selection interface controller for providing an interface for a user to select to open the stored file for the summary portal page; and

responsive to the user selecting to open the stored file for the summary portal page, the summary portal generator for dynamically generating the summary portal page displaying the 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 metadata stored at each of the plurality of different times.

16. The system according to claim 9, the summary portal generator for dynamically creating the summary portal page graphically distinguished from at least one other portal page and comprising a summary of said stored usage within at least one of a separate window and a tabbed window.

17. A program product comprising a storage-type computer-usable medium 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 usage metadata indicating current usage of at least one portlet within at least one portal page for one of a plurality of events specified to trigger storage of the usage metadata;

responsive to detecting one of the plurality of events within the usage metadata, store the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page;

subsequent to storing separate detected usage metadata at a plurality of different times, 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 separate usage metadata stored at each of the plurality of different times;

present a graphical user interface for a user to select to save the summary portal page in association with one of a plurality of calendar events; and

responsive to a user selection of at least one particular calendar event from among said plurality of calendar events, store a portlet specification of the summary portal page in association with the at least one particular calendar event.

18. The program product of claim 17, wherein the computer-readable program is transmitted over a network.