[gradebook2-dev] Problems with GB2 services and grades integration

[Thomas Amsler]

If the comment was provided via an external tool, such as Assignment,
etc., then we should disable the edit comment button. If this is the
case, please create a JRIA for this. Thank you.

Best,
-- Thomas

On Wed, Aug 31, 2011 at 3:13 AM, Jose Rabal Sastre <joserabal at um.es> wrote:
>  Hi again. I tried to reproduce the error on gb1 to assign the jira to
> the edu-services team but I saw that the error cannot be reproduced
> there because in gb1 the "Edit comment" button is disabled for external
> grades (and there is no "excuses" option either). Perhaps should be the
> same behavior in gb2?
>
> El 31/08/2011 5:51, Jon Gorrono escribió:
>> On Tue, Aug 30, 2011 at 2:51 PM, Jon Gorrono<jpgorrono at ucdavis.edu>  wrote:
>>> Hi, Jose.
>>>
>>> see inline
>>>
>>>
>>>
>>> On Tue, Aug 30, 2011 at 4:39 AM, Jose Rabal Sastre<joserabal at um.es>  wrote:
>>>>   Any grade with "comments" or "excuses option" selected causes the
>>>> constraint violation error when an external tool tries to remove it
>>>>
>>>   remove the comment?
>> Ok, stupid question since you can't remove comments.
>>
>> I can reproduce the constraint violation and the warning which
>> effectively keeps the assignment from being associated with the
>> gb...by using this process:
>>
>>
>> first: tail --follow catalina.out
>>
>> - in assignment tool create an assignment and associate it with GB
>> (not a existing item), give some points, instructions
>> - in gb2, add some comments on the item for a student
>> - in assignment tool, edit the assignment and remove the GB
>> association... (this is where I expected to see fireworks)
>> - in gb2 right clock and rollover edit comment on item
>> - in gb2 delete the item
>> - in assignment tool
>>
>> Would you create a jira for this?
>>
>> Thank you.
>>
>>>> and it
>>>> has nothing to do with removing the grade from gb2.
>>>>
>>>> Also If we remove an external grade with comments from gb2, the external
>>>> application can not send it again and log shows the message:
>>>>
>>>> 2011-08-30 12:10:02,578  WARN http-8080-Processor25
>>>> org.sakaiproject.tool.assessment.ui.listener.author.SavePublishedSettingsListener
>>>> - oh well, must have been added already:An external assessment with that ID
>>>> already exists in gradebook ui
>>>> d=fa0a5450-44cf-41b3-a8a4-7e24b2249137
>>> i see.... I'll try to reproduce all this again later tonight
>>>
>>> Thanks
>>>
>>>
>>>
>>>> I reproduced the error on a clean Sakai 2.7.1 and Gradebook2 1.6.1
>>>> installation.
>>>> I will report the issue to edu-services team too.
>>>>
>>>> Thank you!
>>>> Jose Rabal
>>>>
>>>> El 30/08/2011 1:55, Jon Gorrono escribió:
>>>>> As far as I can determine from this description and some testing of my
>>>>> own, if there are issues, then they need to be addressed by the
>>>>> edu-services maintainers .... Gradebook2 uses the same tables as does
>>>>> Gradebook2  and those are in edu-services...IOW, deleting an
>>>>> assignment from GB1 would obviously delete it from GB2 since they
>>>>> reference the same data, and if you think that removing the 'publish
>>>>> this to gradebok' relationship from the item in assignments should
>>>>> delete the item from GB1 and GB2, then that should be raised with the
>>>>> right development team: edu-services... we'd be glad to participate in
>>>>> any discussions, however.
>>>>>
>>>>> WRT to the specific constraint error: this would occur if a comment
>>>>> were referenced for which there was no corresponding gradable object.
>>>>> Is it possible you removed the assignment from gradebook and with a UI
>>>>> (browser window) that was not refreshed with that 'knowledge', and
>>>>> then tried to edit the comment?
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Aug 29, 2011 at 5:46 AM, Jose Rabal Sastre<joserabal at um.es>
>>>>>   wrote:
>>>>>>   Hi everyone!
>>>>>> This is Jose Rabal from the University of Murcia in Spain. We are
>>>>>> experimenting some errors in Gradebook 2 with grades that have been sent
>>>>>> from other tools like Samigo or Assignments to GB2. If we add a comment
>>>>>> in one of this grades and later we try to specify that we don't want to
>>>>>> send it to gradebook, the console shows the following error
>>>>>>
>>>>>> ERROR org.hibernate.util.JDBCExceptionReporter  - Integrity constraint
>>>>>> violation FK7977DFF06F98CFF table: GB_COMMENT_T in statement [delete
>>>>>> from GB_GRADABLE_OBJECT_T where ID=? and VERSION=?]
>>>>>>
>>>>>> and the grade is not removed from Gradebook.
>>>>>>
>>>>>> If we remove the grade using the Gradebook tool then the grade
>>>>>> dissapears, but if we set in Samigo or Assignments that we want to send
>>>>>> the grade again to Gradebook, the grade is not sent again.
>>>>>> I would like to test this error in a QA server with Gradebook 2, but all
>>>>>> the servers that I have found are with Gradebook 1. Can anyone reproduce
>>>>>> the same problems? I have tested the error on Gradebook 1.3.0, 1.5.0 and
>>>>>> 1.6.0, Sakai 2.7.1 and 2.8.
>>>>>>
>>>>>> Thanks in advance!
>>>>>> Jose Rabal
>>>>>> _______________________________________________
>>>>>> gradebook2-dev mailing list
>>>>>> gradebook2-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/gradebook2-dev
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Jon Gorrono
>>> PGP Key: 0x5434509D -
>>> http{pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
>>> GSWoT Introducer - {GSWoT:US75 5434509D Jon P. Gorrono<jpgorrono - gswot.org>}
>>> http{sysdev.ucdavis.edu}
>>>
>>
>>
>
> _______________________________________________
> gradebook2-dev mailing list
> gradebook2-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/gradebook2-dev
>