[sakai2-tcc] Roster2 replacing Roster Classique

[Steve Swinsburg]

It would be useful to see what the use cases are, and see if they can be handled already,so yep post out a request.

Cheers,
Steve 

Sent from my iPad

On 19/06/2012, at 20:56, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> I got the impression from some other folks at the conference and in
> this thread that they needed the functionality to be like Adrian
> described. Maybe we should post something to the dev and production
> list and outline the 2 options (which I think are control in roster2
> or control in profile2 right?).
> 
> I am happy to post it if you would like but it's probably easier for
> Adrian at this stage.
> 
> Thoughts?
> -AZ
> 
> 
> On Tue, Jun 19, 2012 at 6:52 AM, Steve Swinsburg
> <steve.swinsburg at gmail.com> wrote:
>> I thought the idea was that roster2 would just delegate all image requests
>> to profile2. So it didn't have the option for one or the other, it would
>> just show an image.
>> 
>> You will hit the problem where the cool uploaded image actually is the
>> official image, since users can activate that and it will override in
>> profile2. I don't see a lot of value in retaining the radio button to toggle
>> between.
>> 
>> An institution can configure what images are shown p, and what users are
>> able to set themselves, in the settings for profile2. If people really want
>> to be able to see both, it needs much more work.
>> 
>> Off the top of my head you will need to extend the profile2 image entity
>> provider to pass in an option to specifically request official images.
>> You'll then need to do some work in the profileimagelogic API to expose a
>> method that returns the official profile image. I'm not sure I'd be a fan of
>> splitting that since the goal was that there would be one method that
>> everyone calls no matter what, and it handles everything from privacy to
>> preferences, and always returns something.
>> Right now, all options are handled in the one method, getprofileimage, which
>> could easily be extended right now to handle the filesystem official images.
>> 
>> Small change in behavior of how the roster works, but I think it will still
>> capture all use cases that people have.
>> 
>> cheers,
>> S
>> 
>> 
>> Sent from my iPad
>> 
>> On 19/06/2012, at 18:13, Adrian Fish <adrian.r.fish at gmail.com> wrote:
>> 
>> I don't think that's quite right. We need the radio button so that roster
>> users can pull the official images even if the student has selected to show
>> their cool uploaded one. In other words we need to circumvent profile2 under
>> that circumstance. I think ...
>> 
>> Cheers,
>> Adrian.
>> 
>> On 19 June 2012 09:09, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
>>> 
>>> Yup we just need the filesystem photo storage as an option in the official
>>> images. Then we are good to go. Profile2 takes care of the rest.
>>> 
>>> cheers,
>>> s
>>> 
>>> 
>>> On Tue, Jun 19, 2012 at 7:40 AM, Adrian Fish <adrian.r.fish at gmail.com>
>>> wrote:
>>>> 
>>>> I think the general gist here is that some of the old roster
>>>> functionality needs porting to Profile2. I'll take a look at the specific
>>>> JIRAs mentioned in the thread. If we are to turn profile and roster
>>>> classique off then we need to get it all.
>>>> 
>>>> Boom!
>>>> 
>>>> 
>>>> On 18 June 2012 22:36, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>>>> 
>>>>> That's how we like to roll up in the TCC. Boom!
>>>>> -AZ
>>>>> 
>>>>> 
>>>>> On Mon, Jun 18, 2012 at 5:34 PM, Adrian Fish <adrian.r.fish at gmail.com>
>>>>> wrote:
>>>>>> That's right, bring it on. Lure Adrian in with a simple bit or Roster2
>>>>>> work
>>>>>> then drop the grand piano on him.
>>>>>> 
>>>>>> 
>>>>>> On 18 June 2012 22:31, Seth Theriault <slt at columbia.edu> wrote:
>>>>>>> 
>>>>>>> On Mon, Jun 18, 2012 at 2:47 PM, David Horwitz
>>>>>>> <david.horwitz at uct.ac.za>
>>>>>>> wrote:
>>>>>>>> Ours are on a filesytem store - I wrote a provider mechanism for
>>>>>>>> profile
>>>>>>>> classic to make it plugable...
>>>>>>> 
>>>>>>> Columbia has a custom PhotoService implementation for Roster to read
>>>>>>> photos directly off our file system. We filed a Profile2 JIRA for the
>>>>>>> same functionality:
>>>>>>> 
>>>>>>> https://jira.sakaiproject.org/browse/PRFL-682
>>>>>>> 
>>>>>>> Seth
>>>>>>> _______________________________________________
>>>>>>> sakai2-tcc mailing list
>>>>>>> sakai2-tcc at collab.sakaiproject.org
>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> sakai2-tcc mailing list
>>>>>> sakai2-tcc at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> sakai2-tcc mailing list
>>>> sakai2-tcc at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>> 
> 
> 
> 
> -- 
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile