Suppress channel on tab if no permission to view it
Tue, 2006-11-21 17:19 — villiam
Has anyone come up with a way to hide a channel that a user does not have access to? What I am after is to create a layout fragment that will be seen by a broad group of users but will have channels that only various subsets of that user base should have access to.
In looking at the XML that is passed to nested-tables.xsl I do not see any attrbitue will can make use of to suppress the data, however I may be missing something.
BTW this is for version III.3.3.
Hack Your Knowledge
Recent blog posts
- Portal for Prospects - facilitation of user accounts from Banner
- receiving error while installing on Solaris
- PermGen space on Windows
- Luminis IV integration with Lotus applications
- Anyone do a complete SunONE migration to Exchange?
- SAF: Is it required if using ILM and Active Directory
- Calendar Migration: SunOne to Exchange 2007
- IMAP on Luminis IV
- cptool list sessions via JSP
- server.policy
Developer Links
Poll
What is your estimated peak concurrent usage (sessions) on Luminis at your institution?
More than 2500
19%
Between 2000-2499
0%
Between 1500-1999
3%
Between 1200-1499
16%
Between 900-1199
5%
Between 500-899
24%
Fewer than 500
32%
Total votes: 37
- Login or register to post comments
- Older polls
Syndicate
hiding a channel
Hi,
I think this behaviour is in uPortal later versions - http://www.ja-sig.org/wiki/display/UPC/Filtering+Channels+within+DLM+Fragments - you might be able to back port code, if you can find it... (it would be a cool function to have).
rich
As well as Lum IV
I also believe this will be present in Luminis IV. After I posted my question I played a bit more and at present have some JavaScript that will automatically hide the channel once the page is loaded.
In looking at the XML produced for the nested-tables.xsl there were no attribtues on the channel element I could use to prevent outputting it.
I am going to play with having the channel automatically remvoed via JavaScript at which point I will post some instructions on this.
Controlling Channel Display Based on Time/Date Stamp...possible?
Did you ever get your JS example working yet? I'm interested in hiding a channel based on a time stamp. Your suggestion might work for this as well.
Thanks.
- buck
I did ...
I did work out some JavaScript that does this and can be seen here: Automatically hide/remove unauthorised channels.
Todd made a good point that may or may not be an issue for your institution.
instead of channels use full tabs
There have been two ways that we have accomplished this in the past. (this is assuming that you know how to add custom roles, if you don't, I can post about that also).
1. Use a targeted content channel with role based content. You can make a section that can only be seen by 'role A' and a section by 'role B'. This is assuming that you are Ok with both role A and role B having some channel in that area. The content would be different for both.
2. Using an entirely new tab for role A vs role B. Another method we have used, is to basically duplicate an entire tab, and remove 1 or 2 channels from it, and assign it to role B in place of the old tab.
We have started to use method 2 more often, as targeted content has some pretty big performance impact, and having a new tab set for different roles provides much more flexibility.
This can cause some extra maintenance though, so you need to be thoughtful about how you create your channels. Try to avoid redundant information, and try to truly 'channelize' content, so that if multiple roles and tabs have a need for specific content, it should be in one channel.
For example, if you made completely different home tabs for employees, faculty, and students, and they all need contact numbers, help desk, etc.., put all the numbers that are generic into one channel, called "Contacts" or something. And then put role specific contact numbers into a second channel, as opposed to making "Employee Contacts", "Faculty Contacts", etc.. and repeating many of the same numbers.
We have all the standard roles, and have added a custom one recently called "non-credit". This is driven by Banner logic.
Good thoughts
Hey Jason some good thoughts there. We do try and use #1 where possible and since go live have used #2 prior to my post.
The issue with #2 is that we have a group of users that are in multiple roles (student, faculty and employee) as such where we duplicate tabs with minor differences for each role these users get multiple copies of tabs.
We can control which tabs override others via the DLM settings however this is not entirely perfect as a grad student who is teaching some first year courses still needs access to the student specific channels as well as the faculty specific ones.
Fortunately as it is a portal, that user can adjust their tabs to make them work the best for them. :)