Re: [uportal-dev] Popular portlets portlet
As an Admin I'll likely want to retrieve the list with counts in two cases: * To satisfy an on-demand query: "What are the portlet names and counts right now for the last week or month?" * To retrieve and archive statistics: "What were the portlet names and counts for February?" As a non-Admin, I'd likely want to retrieve the list in one case, and having the counts show is okay: * To satisfy an on-demand query: "What are the portlet names (counts okay too) right now for the last week or month?" I'm not sure what options you have with subflows of the portlet-manager. I suspect a single portlet would cover both Admins and non-Admins, even if I had to list the portlet twice with a different portlet preference/parameter to turn on/off features. A question I have about the portlet picture attached. It uses paging. How would I get a complete list in one view to archive the list? Would it be an Admin feature to get a CSV file, or something? Cut/Paste would work for me, assuming everything was in one place to snag it. Would the focused view be a complete list? On Fri, Mar 18, 2011 at 3:32 PM, Drew Wills wrote: > I've prototyped a new framework portlet that provides a report of > "Popular Portlets" -- which portlets have been added to layouts by users > and how often. I'm attaching a screenshot. > I'd like to pick the brains of those on this list over this question: > what use(s) should we put this portlet to? > > Option 1: For admins > -- > Provide either a new portlet, a subflow off of the portlet-manager, or > both. Admins can use the full power of the portlet to audit which > portlets are popular with users who customize their layouts. > > Option 2: For everyone > > Provide a portlet with perhaps limited features (maybe can't see counts, > can't see as far back, etc.) for everyone. This portlet could help > users become aware of portal content they might be interested in. > > Please share your thoughts on these use cases, what titles & > instructions should appear on the UI, etc. > > thanks! > > drew wills -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
Re: [uportal-dev] Popular portlets portlet
Drew, Fantastic! I think it would be good to support both Option 1 and Option 2. I know of popular use cases for each. For Option 1 (Admin), I could see where having the ability to see what portlets are most used within the Portlet Manager would be good. It could also be a standalone portlet that resides alongside the portlet manager in the admin dashboard. In this context, I would suggest the title to be "Most Added Portlets". For Option 2 (Everyone), this portlet seems like a good default for most institutions for the general populace (assuming end-user customization is allowed). People new to the portal could see what is "most popular". In this context I would use the title: "Most Popular Apps" or something similar. Gary - Original Message - From: "Drew Wills" To: uportal-dev@lists.ja-sig.org Sent: Friday, March 18, 2011 12:32:50 PM GMT -07:00 U.S. Mountain Time (Arizona) Subject: [uportal-dev] Popular portlets portlet Hey folks, I've prototyped a new framework portlet that provides a report of "Popular Portlets" -- which portlets have been added to layouts by users and how often. I'm attaching a screenshot. It uses the uPortal database stats, specifically the 'LAYOUT_CHANNEL_ADDED' events (so they must be enabled to use it). The user has specify how far back he/she wants the data to go: 1, 7, 30, 90, or 365 days. Like other framework portlets, it's based on a webflow. It includes a RESTful, json-based API for accessing the counts. Admins can see all portlets in the report, but non-admins can only see portlets for which they have SUBSCRIBE permission. Users can "click through" the name of a portlet in the report to "use it now." I'd like to pick the brains of those on this list over this question: what use(s) should we put this portlet to? Option 1: For admins -- Provide either a new portlet, a subflow off of the portlet-manager, or both. Admins can use the full power of the portlet to audit which portlets are popular with users who customize their layouts. Option 2: For everyone Provide a portlet with perhaps limited features (maybe can't see counts, can't see as far back, etc.) for everyone. This portlet could help users become aware of portal content they might be interested in. Please share your thoughts on these use cases, what titles & instructions should appear on the UI, etc. thanks! drew wills -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: g...@unicon.net To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
[uportal-dev] Popular portlets portlet
Hey folks, I've prototyped a new framework portlet that provides a report of "Popular Portlets" -- which portlets have been added to layouts by users and how often. I'm attaching a screenshot. It uses the uPortal database stats, specifically the 'LAYOUT_CHANNEL_ADDED' events (so they must be enabled to use it). The user has specify how far back he/she wants the data to go: 1, 7, 30, 90, or 365 days. Like other framework portlets, it's based on a webflow. It includes a RESTful, json-based API for accessing the counts. Admins can see all portlets in the report, but non-admins can only see portlets for which they have SUBSCRIBE permission. Users can "click through" the name of a portlet in the report to "use it now." I'd like to pick the brains of those on this list over this question: what use(s) should we put this portlet to? Option 1: For admins -- Provide either a new portlet, a subflow off of the portlet-manager, or both. Admins can use the full power of the portlet to audit which portlets are popular with users who customize their layouts. Option 2: For everyone Provide a portlet with perhaps limited features (maybe can't see counts, can't see as far back, etc.) for everyone. This portlet could help users become aware of portal content they might be interested in. Please share your thoughts on these use cases, what titles & instructions should appear on the UI, etc. thanks! drew wills -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev<>
