[sakai2-tcc] Roster tool changes

[May, Megan Marie]

My two cents re: feasibility of including this in the 2.8 release?

Even with ANU deploying it soon, I do not feel that it has had enough production experience to be included in the foundation release package for 2.8.   

-----Original Message-----
From: sakai2-tcc-bounces at collab.sakaiproject.org [mailto:sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of Daniel Robinson
Sent: Thursday, August 19, 2010 10:17 AM
To: csev
Cc: Sakai 2 Technical Coordination Committee; Adrian Fish
Subject: Re: [sakai2-tcc] Roster tool changes

Hi Chuck,

Thanks for the response.

You're correct, the Roster tool is a "read-only" tool and doesn't  
interact with the database directly

Our intention is that the refactored Roster tool will work with a  
number of recent releases of Sakai. As far as I know, it doesn't  
depend on any recent changes to the services used, but does require  
EntityBroker 1.3.13 or higher.

We have paid interest to accessibility concerns and hope we have not  
reduced the accessibility of the tool in any way. We would welcome  
feedback on this area from those with the experience.

It was our original intention to have this new version of Roster in  
the 2.8 release, but understand that this may be pushing it a bit. We  
do have this running in production, but are not using it for course  
sites with enrolments as we don't use those at Lancaster. We have  
tested the new version using the Sakai sample course data, but that is  
no substitute for real world tests.

Does anyone else have a comment about the feasibility of including  
this in the 2.8 release?

Best wishes,

Daniel

On 19 Aug 2010, at 14:20, csev wrote:

> Dan/Adrian,
>
> Looks like good stuff a few questions.
>
> -  It appears as thought this makes no changes to any database  
> information so there is no conversion necessary - cool
>
> -  The "data model" is SakaiProxyImpl.java - and this just calls a  
> bunch of existing Sakai services to produce a service which gives a  
> roster-view of existing Sakai data - cool.   I am curious how tricky  
> this code is - would it work with a number of recent Sakai releases  
> or does it depend on recent changes to the services it calls?  There  
> is no wrong answer - more of a curiosity.
>
> - With the switch to trimpath, it would be good to get an  
> accessibility review by someone outside the team just to make sure  
> that it is as good or better than the old tool - I see you have  
> fixed some accessibility things - so I would guess this is already  
> on your minds - but a third-party look at it when you are ready  
> would make everyone more comfortable, I think.  For me personally, I  
> would like to understand better the impact of using trimpath in  
> general on accessibility as per the experts.
>
> We are looking at code freeze in the third week of September for 2.8  
> - we wondered if Roster might be trying to squeeze into 2.8 before  
> the freeze.    At this point with 4-5 weeks remaining, it would seem  
> a bit of a stretch to put this into 2.8 on that time scale unless  
> someone was running it in production somewhere.    Feel free to  
> clarify if I misunderstood.
>
> Again, thanks - this sounds like good stuff we all will benefit from  
> and in my short review the code looks nicely self-contained that  
> will drop in pretty painlessly.
>
> /Chuck

_______________________________________________
sakai2-tcc mailing list
sakai2-tcc at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc