[Building Sakai] Upcoming content-review/assignments changes

Stephen Marquard stephen.marquard at uct.ac.za
Thu Jul 3 05:17:57 PDT 2014 

A2 does have a 10.x branch which builds and runs with Sakai 10.x:

https://source.sakaiproject.org/contrib/assignment2/branches/sakai-10.x/

Regards
Stephen

---
Stephen Marquard, Learning Technologies Co-ordinator
Centre for Innovation in Learning and Teaching (CILT, formerly CET and HAESDU)
University of Cape Town
http://www.cet.uct.ac.za<http://www.cet.uct.ac.za/>
stephen.marquard at uct.ac.za<mailto:stephen.marquard at uct.ac.za>
Phone: +27-21-650-5037 Cell: +27-83-500-5290

From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Bryan Holladay
Sent: 03 July 2014 02:14 PM
To: Matthew Jones
Cc: sakai-dev
Subject: Re: [Building Sakai] Upcoming content-review/assignments changes

Ok, I'll leave the patch in the Jira for TII.  I'll contact Michelle to see if she is still leading A2 or not.  I agree, A2 should be branched (if it hasn't) for the 10x release since it won't be compatible now.

-Bryan

On Wed, Jul 2, 2014 at 11:48 PM, Matthew Jones <matthew at longsight.com<mailto:matthew at longsight.com>> wrote:
Earle has the last commit for TII, but that was over 6 months ago. I'd guess there is no *lead*. I believe that branch/api is supposed to stop working/being supported soon so if this is just for trunk it might not be too useful.

Prior to that, nobody except for David Horwitz and Earle have made commits to that trunk for almost 3 years.

The last commits to A2 are from Michelle.

Is this compatible with what's currently in 2.9/10? I think if you are changing TII you should branch it around so everything is compatible with what's there and people know what to use.


On Wed, Jul 2, 2014 at 9:06 PM, Bryan Holladay <holladay at longsight.com<mailto:holladay at longsight.com>> wrote:
This work has been committed into trunk.  I'll keep an eye out to make sure the builds aren't broken.

I have two pending contrib patches that I don't have access to commit.  Who is the lead for the contrib TII content review impl project and the Assignments2 project?  Both patches are ready to go and both tools will be broken until they are patched.

A2:https://jira.sakaiproject.org/browse/SAK-26601
TII: https://jira.sakaiproject.org/browse/SAK-26602

Thanks
Bryan

On Fri, Jun 27, 2014 at 2:13 PM, Bryan Holladay <holladay at longsight.com<mailto:holladay at longsight.com>> wrote:
This part will actually be added as the default impl for content-review in the content review project: https://github.com/LongsightGroup/contentreview-federated.git

On Fri, Jun 27, 2014 at 2:02 PM, Brian Baillargeon <bbailla2 at uwo.ca<mailto:bbailla2 at uwo.ca>> wrote:
Bryan Holladay and I have both committed to branches, and we're nearly ready to merge into trunk.
In summary, we've:

  *   replaced hard coded references to 'Turnitin'
  *   allowed other content-review services / multiple services to run side-by-side
  *   fixed issues where assignment submissions existed; instructors changed the accepted submission types; student submissions were no longer accessible or they could submit content that was no longer accepted
  *   allowed multiple attachments and inline submissions to be submitted to the content-review service
But we need a few things to happen before this gets merged.

Firstly, we will need somebody to look at KNL-1267. I think it's good; it just needs more eyes. It's depended on by SAK-26329 which is depended on by SAK-26322 which is a subtask of SAK-26318. Can anybody on the KNL team take a look?

Secondly, who maintains the Turnitin content review implementation (https://source.sakaiproject.org/contrib/turnitin/trunk/)? Neither of us have commit.

Again, here is the master ticket:
https://jira.sakaiproject.org/browse/SAK-26318

Here are the branches that we have committed to:
https://source.sakaiproject.org/svn/content-review/branches/SAK-26318
https://source.sakaiproject.org/contrib/turnitin/branches/SAK-26318
https://source.sakaiproject.org/svn/assignment/branches/SAK-26318

And these are for Longsight's content-review service, VeriCite:
https://github.com/LongsightGroup/contentreview-federated.git
https://github.com/LongsightGroup/contentreview-impl-vericite

Thanks,
Brian Baillargeon


On 14-06-10 03:53 PM, Bryan Holladay wrote:
This is being tracked under https://jira.sakaiproject.org/browse/SAK-26318 and targeted for trunk.

On Tue, Jun 10, 2014 at 3:47 PM, Brian Baillargeon <bbailla2 at uwo.ca<mailto:bbailla2 at uwo.ca>> wrote:
FYI to avoid duplicated efforts:

Bryan Holladay and I will be making the following modifications to content-review as well as assignments:

  *   Adding a federated content review service.

     *   You will be able to run multiple content-review services side by side.

  *   Cleaning up hard references of "Turnitin" / Turnitin specific configuration.

     *   All references will point to your actual content-review service.

  *   Multiple attachments as well as inline submissions will be content-reviewed.

     *   Currently, only one attachment can be content-reviewed per submission; inline submissions are never reviewed.

  *   The content-review api will provide a call to upload multiple resources and a call to retrieve multiple reports at once.

     *   This will improve performance if your content-review service implementation uses, say, a web-service as opposed to the contentreview_item table.

  *   The student's view of an assignment will always reflect the assignment's accepted submission type; students will always have access to their previously submitted material.

     *   Currently, if a student tries to resubmit after the instructor has changed the assignment's accepted submission type (ie. from Inline & Attachments to Inline only), the student may not have access to their previously uploaded material or they may continue to submit attachments/inline text when it is no longer accepted.

-Brian Baillargeon

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"





_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"


________________________________
UNIVERSITY OF CAPE TOWN

This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140703/1b29ff8f/attachment.html

More information about the sakai-dev mailing list