Posted by bob_irving on February 19, 2009 at 2:09pm
I've had some requests from tutors to view my class's assignment calendar. I'm using Bill's model from his book and have the assignment calendar up and running.
I would like these people to be able to view the calendar and the assignments but no more. I'm not sure how to do this. I tried to create a new role (calendar viewer) and assign just those rights, but those are not options. I also looked at the View for the assignment calendar but am frankly stumped. I don't particularly want to add these people to the class, just because I'd like to have some measure of privacy for the students.
Any suggestions?
Comments
You can set permissions for
You can set permissions for a View from the View's edit page. Then set the view to role based permissions and select the roles that can view it. You'll need to make sure that the content visible on the calendar is visible by the role as well since it'll obey display permissions and hide things on the calendar accordingly. Might want to use this stuff in conjunction with Node Privacy by Role so that you can make it so this new role can only see assignments and not other types of content.
"Plaguing the world with Drupal; One Plone, Moodle, Wordpress, Joomla user at a time since 2005." ~ btopro
http://elearning.psu.edu/
http://elearning.psu.edu/projects/
http://elearning.psu.edu/drupalineducation/
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
What Bryan said, and...
In the View settings, in the Basic settings section, you can set the visibility settings for the entire view.
Then, if you want to let the tutors see a subset of data without giving them any more access (or without using another access control module) you can use either the Node: Published or the Node: Published or Admin filter. The Node:Published or Admin filter will respect access controls. The Node: Published filter will show the content of the view to people who can see the view. If, however, a user then tries to click through to the full node, they would get an access denied.
This has worked for me in setting up table views; I have yet to try it with a Calendar view, but I'm assuming it would work in the same way.
Cheers,
Bill
FunnyMonkey
Click. Connect. Learn.
Using Drupal in Education
FunnyMonkey
another fix
A workaround, actually.
I decided that letting them view the content wasn't really the issue I originally thought it was. So I created a "tutor" role and gave them access to content. For my purposes, that will probably work. Hopefully, I haven't forgotten some key aspect here.
Multiple Site Set Up And Management Using Bill's Book Model?
I've set up a website using the information and guidance provided in Bill's book. My question is how do you set up and manage multiple sites for various instructors and their classes?it
Options, options
I remember the book correctly, Bill had you install Organic Groups, so I'm assuming that by "multiple sites for various instructors" you are looking for something beyond what you get by giving each instructor a Group.
There are a couple of approaches for doing this. I guess that goes without saying ;). The two I have tried out are subdomain sites and a module called Domain Access. With the subdomain approach, you basically install a new database for each new site. All the sites run off the same drupal install folder, but each site has it's own settings.php file, it's own files folder, and it's own database. This keeps your sites nicely separate, but it also means that you have lots of databases to maintain. Also, I've found that subdomain sites can be tricky. They don't behave EXACTLY the same way that single domain sites do, and that can be frustrating.
With Domain Access, every site runs off of the same database. You can separate the content, the users, the menus, the themes, but you can also keep any of these elements the same across all domains. It's all done through a rather daunting set options, but the basic trick is to decide which database tables to make copies of for each domain, and which ones to share. I'm not sure it makes a lot of sense to dive into Domain Access unless you actually have content you'd want to share across sites, but even if you don't it at least means you only have one database to manage.
I only just started playing with Domain Access this past weekend, so I won't go out on a limb and recommend it just yet. Just thought I'd mention it as an option to check into.
Of course, it is also possible to do a fresh drupal install for each instructor. I wouldn't recommend it, but if you do want to go that route, you can clone any existing database to give yourself a headstart in terms of enabling modules and putting in any starter content. The same can be said for subdomain databases.
Thanks Becky For Your Comment.
I do appreciate you sharing your thoughts on the subject with me. Kudos.
OG will work in most cases
Depending on your specific needs, Organic Groups will work well, especially if all your classes have the same basic needs. If you have widely varying needs by class, then the Domain Access module would be a good next step. Also, if you have a wide age range, you might want to create multiple sites with OG that group students by age (ie, K-5; 6-8; and 9-12).
With more info on the age range, the types of classes, and the activities in the classes, we could narrow things down a bit more.
Cheers,
Bill
FunnyMonkey
Good Job Bill.
I can't thank you enough for taking time off your busy schedule to reply to my post. You've made my day.