Imported assessment keeps old course name for "released to" field

Description

Steps to reproduce:

Create an assessment and export it using either QTI v 1.2 or Content Packaging.
Import the assessment into another course with a different name.
From the list of pending assessments, choose publish from the combo box next to the imported assessment.
On the publish assessment page, click publish.

As a result students cannot see the assessment to take it.

Attachments

1

Activity

Show:

George Pipkin February 2, 2015 at 12:11 PM

At U.Va. I encountered a problem in which imported eTap polls that are specified in the fiule to be released to "Anonymous Users" do not have that value set automatically in the unpublished assessment resulting from the import. I traced the problem to several lines of code in AuthoringHelper (~726):

String siteTitle = SiteService.getSite(ToolManager.getCurrentPlacement().getContext()).getTitle();
if(siteTitle != null && !siteTitle.equals(assessment.getAssessmentAccessControl().getReleaseTo())){
assessment.getAssessmentAccessControl().setReleaseTo(siteTitle);
}

In this case releasedTo is subsequently used to set the "Assessment released to" pulldown on the settings page. Since this pulldown
can only have one of three values, "Anonymous Users", "Entire Site", or "Selected Users", setting it to the Site Title effectivly causes the
pulldown to always be pre-set to the first value, "Entire Site".

I commented out this code, and it resolved the problem mentioned above. With the code still commented, following the steps to reproduce mentioned in I exported another quiz, and re-imported it to another site. I noted that the imported quiz, when published, was available to students on the site as it should be.

So, I'm wondering what the purpose of this change is. It appears, from my own testing, that the problem mentioned in does not rear its ugly head with or without the patch contained in SAM-1350. And with those lines of code in play, a regression appears related to import of eTap polls.

Derek Ramsey October 10, 2013 at 9:45 AM

Using the provided steps to reproduce, I can not duplicate the behavior on trunk.

http://nightly2.sakaiproject.org:8082/portal
Built: 10/10/13 08:00 - Sakai Revision: 130298 (Kernel 2.10-SNAPSHOT)

Sam Ottenhoff October 4, 2013 at 2:52 PM

Thanks Kevin.

Trunk commit r130191.

Neal Caidin October 4, 2013 at 1:07 PM
Edited

per 2.10 patch review meeting, proceed with commit. Taken by Sam O.

Kevin Takacs August 31, 2011 at 1:37 PM

I attached a patch that checks the released to value and sets it to the title of the destination site if they do not match.

Fixed

Details

Priority

Affects versions

Fix versions

Assignee

Reporter

Created August 31, 2011 at 1:33 PM
Updated February 3, 2019 at 11:01 AM
Resolved October 4, 2013 at 2:52 PM