The Facebook stuff probably does deserve its own thread. I only mentioned it because the notification stuff would be involved and because it would have to be pushed to Facebook, so there may not be a user created event to trigger things.
As for authentication, I've not thought that through. I've been running with the assumption that some part of adding the Facebook app involved registering their Facebook-associated email address with a portal userid and using the university's email system to mail out a confirmation to their university email address. On Thu, Dec 22, 2011 at 3:30 PM, Jen Bourey <[email protected]> wrote: > Hi Bruce, > > Thanks for the feedback! > >> (A) If we are talking about having many notification portlets in a >> portal, each specific to certain content/sources, then... >> >> (A1) When a portlet has one or more things to be considered a >> notification, that the portlet be adorned with a badge indicating how >> many notifications are associated with that portlet > > We've actually already implemented some badge numbers support in uPortal 4 > using portlet request properties. We're not displaying any of that > information yet on the desktop side, but the courses portlet shows an example > badge number in the mobile view. I think it would be great to eventually > integrate these new badge numbers into the desktop theme. > >> (A2) When a tab on which one or more portlets with notifications, the >> tab be adorned with a badge indicating the total number of >> notifications. > > Sounds terrific to me, and this seems to line up with Anthony's suggestion as > well. I'm not quite sure how we'd implement that technically, since the > current badge number values aren't visible to the theme transform. > Definitely something it would be good to explore though. > >> (A3) A portlet with a notification could have some alternative >> coloring for its chrome. For instance, if the portlet's chrome is >> normally a dark green, it might be a brighter green when it has a >> notification. >> >> (A4) A tab containing portlets with notifications could have some >> alternative coloring for the tab. > > Once again we'd need to think through the technical options for implementing > something like this, since content rendered by a portlet (or events, or > request properties, etc.) aren't really visible to the theme. I like the > idea though. > > >> (B) If we're talking about having a single notifications portlet that >> assembles a great many notifications from many sources, then I'm not >> sure how I'd like it to behave. On one hand I like having all the >> notifications in one portlet so you only have to look in one place, >> but on the other hand it will be a collection of unrelated >> notifications and there will not be enough screen real estate to >> surround it with portlets of similar content. >> >> For instance, does a "Your overage check is available" notification >> appear on a "Home" tab along with things like email, or does it appear >> on an "Accounts" tab along with other billing and financial aid >> content? > > I guess my thought was that individual portlets might still have > notifications, but that the notifications portlet could be a good dashboard > for collecting notifications across the portal. That way the notifications > portlet might display a notice about your overage check on the portal's home > tab, but a financial portlet might still display that information in the > accounts tab. The notifications portlet might even display a short version > of that notification that then links to the financial portlet for more > information / the ability to act on the notification etc. The notifications > portlet already has an interface that divides notices by collapsible > categories, so that might help with screen real estate. > >> >> (C) Something I've been considering is how to co-op Facebook with our >> Portal. In effect, our students have already largely chosen Facebook >> as their personal portal. What they have suggested to me is to offer a >> "My OHIO" application in Facebook, which integrates with our portal >> and turns portal content into Facebook application notifications. >> >> The end result would be that students would see notifications in >> Facebook, click on them, be taken to the facebook "My OHIO" >> application (hosted on our portal), see the notifications, and then be >> able to click through right into the portal to do something about the >> notification. In effect, the Facebook application would be an >> extension of our portal and lead students to the portal. > > That's a terrific idea, and maybe deserves it's own thread. I think it would > be pretty easy to expose an individual portlet to Facebook via an IFrame - > the bigger challenge is more the authentication bit. We could rely on the > user to already have a CAS/whatever session, or display a login box when they > aren't authenticated, which may or may not be helpful. We could also > consider doing something like allowing the user to authenticate to the > portlet via OAuth, though at that point I think we'd need to consider > creating a concept of weak authentication such that a Facebook auth wasn't > enough to get to other sensitive portlets. What do you think would work well > for authentication to such a portlet at Ohio? > > - Jen > > > -- > 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 > -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- 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
