We’re not using the Announcements Portlet in MyUW, so wearing that hat, alas, I have no feedback about Madison experiences with this portlet.
Eyeballing this from a uPortal-as-product perspective: * As Anthony mentioned, to the extent that accouncement topics are not uniquely identified by their topic name, whatever they actually are uniquely identified by should be also shown in the admin views. * Along the lines Anthony mentioned, I for one would be thrilled for the Announcements Portlet to embrace being a Framework Portlet and use a tighter integration with the sub-flow machinery etc. for group selection, rather than requiring the group —> portlet role integration path. * The cleaner UIs throughout look great and aligning with the newish styles being adopted elsewhere in uPortal. Tool tips for better understanding the options might help a lot. * I’m skeptical of the usability of the My View tiled mosaic view. Local design expertise beats the drum frequently here that mosaics are well intentioned but just don’t work, that users find them overwhelming, and so more of a single-column list view might be more effective. This is part of what’s behind the present MyUW redesign effort. So, maybe something more blog-like, single column, maybe with some side nav to see what topics are available with how many things in them and navigate between. But hey, one never really knows until one does user testing, and this might even be amenable to some paper prototyping before it has to be coded up to see how users react. * More generally there seems to be a responsive mobile-first movement afoot. :) What do those UIs, those mockups look like at iPhone dimensions? :) * The announcements portlet is opinionated about how announcement information is architected, and has different opinions about that than does the Notifications portlet. I think it’s rather too much a lift to eliminate Topics — and if one wants to go that direction, then perhaps the thing to do is to evolve the Notifications portlet to subsume the Announcements use cases. So given that, I’d be more excited about seeing ways to make the existing information architecture more usable. So, a clearer admin UI about how this works. Maybe administrative convenience for publishing a single Announcement to multiple Topics, as was mentioned earlier in this thread, and then some attention to what it feels like as a user to consume an Announcement that’s been published to multiple Topics, and whether and how that depends on the user’s relationship to those Topics. Kind regards, Andrew From: Cindy Duggan <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, August 7, 2014 at 9:28 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [uportal-dev] Announcement Portlet - Proposed UI Changes Hi, We also encounter the situation where folks would like to target certain groups with the same announcement. So this capability would be very useful for us, too. 2) Assigning permissions at the topic level is not very useful in certain scenarios. E.g. If I have different "Academic notices" for faculty staff and students then I have to create 2 separate topics to achieve this. This gets worse if I want different academic notices for each school. Thanks. Cindy Manhattan College On Wed, Aug 6, 2014 at 5:58 PM, Anthony Colebourne <[email protected]<mailto:[email protected]>> wrote: Hi, I don't really have any UI comments about this project, but I though it worth mentioning some though/discussions I've had about this project. 1) The Assign Permissions feature is too basic. Also mapping the available groups in the portlet.xml is a pain. I think ultimately this need integrating with the Portal groups system. Either by adopting this as a framework portlet or by using uPortal provided APIs. 2) Assigning permissions at the topic level is not very useful in certain scenarios. E.g. If I have different "Academic notices" for faculty staff and students then I have to create 2 separate topics to achieve this. This gets worse if I want different academic notices for each school. The portlet currently allows non-unique topic names, which helps in this scenario as at least each topic can have the same name so users don't know that its actually a different topic. However if you do this, it's impossible to tell in the admin UI which is which without clicking on each one, then clicking back and trying to remember which one you clicked last! Thanks, Anthony. On 06/08/14 21:42, Jodie Muramoto wrote: Hi everyone (again), The next couple of days, I’ll be working on improving the UI for the Announcements Portlet. I’ll be incorporating Bootstrap into the various views, along with adding some PIZZAZZ. Attached are wireframes of some of these ideas. Please note, the color of buttons and the placement of buttons will be addressed, these are simply a general view UI updates. I anticipate having these changes in a pull request later this week. Let me know if you have any feedback or suggestions. Cheers, Jodie Muramoto User Experience | Unicon, Inc. [email protected]<mailto:[email protected]> -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
