[Building Sakai] Question about shopping period settings (DA tool)

[Jim Mezzanotte]

Thanks Bryan. In nightly
(http://nightly2.sakaiproject.org:8081/portal), I'm not getting the
right results. Could you take a look? Here are the steps I've taken:

1. In DA tool, add shopping period for "SUBJ1" node, in DEPT1 of MUSIC.
2. Select "access (!site.template)" for "shoppers become."
3. Add start/end dates (this seems to be required)
4. Click "Show Tools" link, and in popup window select "Syllabus" for
"public" (.anon) role.
5. Add Shopping tool to gateway.
6. Run "Delegated Access Shopping Period" job

When I select sites via the Shopping tool on the gateway, I can access
the sites, but I'm seeing all tools, not just Syllabus. Used FF and
Chrome on OS X, cleared the cache.

I also encountered some inconsistency with access--when I first
selected a site via Shopping, I had to log in, but a few minutes later
I was able to access without login. Assuming the time lag is for the
job running?

Jim Mezzanotte
Asahi Net International









On Mon, Oct 13, 2014 at 7:08 PM, Bryan Holladay <holladay at longsight.com> wrote:
> Shopping period is for opening up specific tools in courses to the public
> (users not required to log in) or private (require users to login). In the
> shopping period settings page, you can select which sites are open during
> specific dates. Those sites will get either the ".auth" or ".anon" role.
> These roles are copied from the selected "user becomes" role. So if you
> select "Student", then anyone who accesses a shopping site will get the
> permissions that a student has. However, this doesn't control what tools are
> shown. The "Choose tools to show" list allows you to specify which tools a
> logged in user can see and which tools a non logged in user can see. All
> other tools are hidden. An example case is opening up just the syllabus tool
> for all courses for only logged in users. This way you can ensure that only
> your institutional users can view any syllabus for any course without having
> to be a member of the course. The shopping tool can be added to the Gateway
> page as a way for students to search and access these sites. The gateway
> page is optimal because non logged in users can access it and search. If you
> only have logged in access for shopping, then it could also just be added to
> MyWorkspace.
>
> On Mon, Oct 13, 2014 at 6:49 PM, Jim Mezzanotte <jmezzanotte at anisakai.com>
> wrote:
>>
>> Hi all,
>>
>> I've been documenting the Delegated Access tool (for Sakai admins),
>> and I have a question about shopping period settings.
>>
>> If you go to:
>>
>> "Delegated Shopping Admin User Use Case"
>>
>> (https://confluence.sakaiproject.org/display/DAC/Delegated+Access+Tool#DelegatedAccessTool-ShoppingUserUseCase)
>>
>> You'll see the following:
>>
>> "You also have the ability to choose which tools are restricted for
>> shoppers by clicking the 'Restrict Tools' link and selecting the tools
>> you want to restrict."
>>
>> But it looks like there's been a change since this was written. Now
>> what you see instead is a "Show Tools" link. When you click this link
>> you get a "Choose Tools to Show" popup window (see attached image). In
>> this window, the text says "choosing a tool in the list will show the
>> tool for this user."
>>
>> So I'm having trouble figuring out how this works. I thought it might
>> provide access to additional tools than what the selected "user
>> becomes" role would provide, but that doesn't seem to be the case. It
>> also doesn't make much sense--it's much easier to restrict access to a
>> tool, since providing access means deciding permissions too.
>>
>> I also tried this as "restrict access in reverse." In other words, do
>> you pick tools to show so that only those tools are accessible,
>> regardless of the "user becomes" role selected? But this also had no
>> effect I could see. I tested with both "public" and "logged in"
>> settings in this window. I'm assuming that "public" only affects
>> behavior if the Shopping tool is added to the gateway, and "logged in"
>> when it's added to My Workspace, but I can't be sure.
>>
>> Apologies in advance if I'm missing something obvious, but I'm stumped
>> on this one.
>>
>> Working in the 10.x maintenance branch
>> (http://nightly2.sakaiproject.org:8081).
>>
>> On a related note--could someone add a prop setting for this instance?
>> The setting is:
>>
>> delegatedaccess.siteaccess.instructorViewable=true
>>
>> Need this functionality enabled in Site Editor to confirm/document the
>> "advanced" shopping admin settings ("disable instructor override" and
>> "disable 'public' option").
>>
>> Thanks in advance for the help!
>>
>> Jim Mezzanotte
>> Asahi Net International
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>
>