I'm trying OA2 in an educational setting where I'm housing subjects and courses in spaces and sub spaces and trying to use the tasks/worktracker component to have students be assigned and then submit (and resubmit if necessary) content which eventually would be marked complete by a staff member. I'm running into some issues using tasks though.

So first, when I create tasks I have the ability to assign the task and its components to a student. The goal is to have the student see that task on their dashboard (or in the space) AND be able to submit something as an attachment WHILE changing the status field in the task.

When I log in as the student, I see the task fine but don't have the option to open the task for editing in order to change the status. So essentially, the student can see the content added to that task but can't do anything with it other than read it.

I assume this is a permissions issue but could find anything relating to tasks under People > Permissions. If I fix that, I could add a media section where a student could attach their assignment however I'm thinking that might not be the best idea either as A. they now have access to mess around with the body field of the task and adjust notifications/owners, etc. AND even if they didn't, there's a lot of extra stuff they don't need. I'm essentially just looking for a dropbox here.

Any insight would be appreciated.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kfurst@isd186.org created an issue. See original summary.

kfurst@isd186.org’s picture

Issue summary: View changes
dpoletto’s picture

To solve your request I think you should start to work with differentiated Groups of Users (as example: Teachers/Students/Staff) and then you will be able to differentiate permissions of each involved Group (which one will be inherited member of the Space into which the Task Section/Sections you're referring to is/are created) regarding to Task Sections and theirs Tasks.

But, at this point (if not yet properly set up), a proper hierarchy categorization of Groups and Spaces shall be necessary and, I think, this subject was yet discussed somewhere here exactly regarding the use of Atrium in Educational environments (see also existing Webinars too).

Available Group Permissions are (considering Group's "non member", "member" and "administrator member" roles):

- Create Task content
- Edit own Task content
- Edit any Task content
- Delete own Task content
- Delete any Task content

Note the own/any differentiation.

To reach (each) Group's Permissions page (Admin -> Open Atrium -> Groups) look at /groups, select the Group you want to edit Permissions from either Membership list or All list, once into the selected Group go to Configure (the wheel icon on the top right) select config and then, finally, you will be able to access the Group's Permissions menu that will land you to its complete Permissions page.

It's important to understand how Atrium works Permissions and what are the roles of Groups/Spaces and also what is the difference between (I had very hard time to understand it) to inherit permissions versus to have child permissions (inheritance options for an Atrium's Group of Users).

kfurst@isd186.org’s picture

Thanks. This helped. I was able to get that permission issue cleared up so this can be closed out.

Though, to be honest, it opened up another issue in terms of best practice for how I want to manage the dropboxing of assignments in regards to tasks and workbench. I saw your note about the webinars. I watched but to provide some constructive criticism, I wish they would go a little deeper than showing a graphic of what you could do/how you could set it up and stopping there. . Most of the webinars and demos are more from the stance of, "Hey, here's why OA is cool and you should try it." I'm already there, man; I need help with the meat not the cheese.

If there's a more tangible walkthrough of an educational production site on YouTube from a Drupal Con or something, I'd love a link.

mpotter’s picture

Well, to be honest, remember that this community stuff is all being done for free and yet I also work for Phase2 and Phase2 is obviously a business that needs to make money. In other words, the "cheese is free", but "you have to pay for the meat" ;)

You might ask drupalize.me or one of the other Drupal training companies if they have anything for Atrium or are planning anything. The more demand they get the more likely they are to offer something. Phase2 works more with large Enterprise clients that need custom Atrium builds or extended and in-depth technical consulting.

kfurst@isd186.org’s picture

@mpotter. Yep. I get it. It just seemed like you guys were pumping out more webinars and vimeo vids in late 2013 or 2014 based on vimeo dates and blog posts on your site. Do you have any webinars/demos coming up?

AND do you know of any universities that are using OA2 that you would be willing to name drop?

Thanks.

Argus’s picture

As someone who contributed to the documentation about Permissions in OA I'm curious how we can improve them. When you wrote this issue in which you assume there is a permission issue did you already read the documentation? If not did the documentation help you enough to get started? If not do you have any tips to improve them?

kfurst@isd186.org’s picture

@Argus

Well yes and no. By that I mean I found Open Atrium via a YouTube vid. I then watched some of Mikes demos on Vimeo and then finally decided to try it out first on a VM and then via Pantheon. I've used Drupal some in the past. I found Phase2's "documentation" site for OA and used that to get started. So I was really approaching the documentation side the wrong way round; I should have read the Drupal docs first and ignored the rest (which I probably would have done if I hadn't found that OA docs site --which is kind of limited).

I just read through the requirements, grabbed the OA zip and spun up an installation. When I went back, the documentation site's section is very clear on the step by step for creating a group or team but I would argue that OA is laid out in such a way that its intuitive for those tasks; I didn't need the step by step. I would also argue what it lacks is the best practice/conceptual understanding of OG needed so that I could figure out how the heck I was going to manage access and permissions for all of these people.

dpolettos' link to the permissions explanation page was what I needed in that I was able to make a connection to how we do roles and permissions for our large scale Moodle deployment currently in use. The biggest "aha" was in the "Don't go about it the Drupal roles way, it won't do anything." I also got a clearer picture that essentially the editor role shouldn't be used in my case. That was must know information since it helped me grasp how it works.

My only personal preference would be that the either 1. The documentation link on the default OA branding homepage that now takes you to the docs site version of OA would instead take you to the Drupal documentation which is much more useful and in depth. OR 2. Things like the Drupal docs permissions explanation page get added to the docs area instead (or I guess in addition to) the section there.

Just my non-expert opinions.