[Building Sakai] Upcoming content-review/assignments changes

[Brian Baillargeon]

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.
>           o You will be able to run multiple content-review services
>             side by side.
>       * Cleaning up hard references of "Turnitin" / Turnitin specific
>         configuration.
>           o All references will point to your actual content-review
>             service.
>       * Multiple attachments as well as inline submissions will be
>         content-reviewed.
>           o 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.
>           o 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.
>           o 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"
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140627/35e331ef/attachment.html