[Building Sakai] TurnItIn Integration

[Steven Githens]

On 11/19/2010 11:02 AM, Adam Marshall wrote:
> So what is the current line of thinking regarding the problem that the originality report displays in the format that the previous site maintainer was using? Is the a query string param that can force a specific version of the report?
>
> This is obviously the catalyst to Raad asking the below mentioned question.
>
>    

Ah, I see.  I'm not sure about this ( although maybe there have been 
some comments in the Jira from TII ).

Upgrade paths are a interesting use case to add to this requirement 
though. Previously it was mostly different departments and parts of the 
university (or perhaps different physical campuses or schools needing to 
use different accounts).

-s

> adam
>
>
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Steven Githens
> Sent: 19 November 2010 15:54
> To: sakai-dev at collab.sakaiproject.org
> Subject: Re: [Building Sakai] TurnItIn Integration
>
> Hi Raad,
>
> Currently the answer is no.  However, this has been a long standing item
> on the wish/requirements list.
>
> During the last round of refactoring to add some functionality to the
> TurnitinContentReview service we factored out all the connection/account
> information into
> org.sakaiproject.contentreview.impl.turnitin.TurnitinAccountConnection,
> which is not independently declared in the spring config, with the idea
> that in the future you can have multiple accounts.
>
> The remaining work that needs to be done includes:
>
> - Adding a database column to the content review items table, so that
> each content item is assigned to a specific account, so when the queue
> processes them they are sent to the proper place.
> - Add overloaded methods to take the account, or just make multiple
> TurnitinContentReviewService components.  Either way keeping the
> original signatures as well with a default account specified. Also add
> the internal logic there to check the site the content item belongs to,
> so you don't have to have the tools themselves check the account.
>
> This isn't currently scheduled to be implemented by anyone, but I keep
> it in mind everytime I need to refactor it a bit for some piece of other
> functionality.
>
> Maximum Cheers,
> Steve
>
> On 11/17/2010 01:11 PM, Raad Al-Rawi wrote:
>    
>> Hi All
>>
>> I have a question regarding the TII integration - is it possible to
>> selectively use multiple TII accounts within Sakai?
>>
>>    From what I know of the integration, I suspect the answer is no, but I
>> thought I would ask nonetheless.
>>
>> The reason is, quite simply, that we would find it useful to be able to
>> specify the TII account on a per-site basis (with a global setting that
>> you could elect to use if not setting a specific account).
>>
>> Is that something anyone else would be interested in?
>>
>> All the best
>>
>>
>> Raad
>>
>>
>>      
> _______________________________________________
> 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"
>