[Building Sakai] Profile/Roster question

Steve Swinsburg steve.swinsburg at gmail.com
Fri Jan 21 21:21:35 PST 2011


Hi David,

In the old Profile tool, users could only enter a URL to an image  of their choice. As far as I was aware back then, the JPEG_PHOTO field was the institutional image store.  Profile2 takes into account any choice or configuration that is set and displays the appropriate image, and the Roster integration handles that. It's just that the file storage method isn't setup to be read for the conversion. Profile2 can handle both user preferred images and official images in the conversion so I've JIRA'd this file store as an option to be read from when doing the conversion, and it will load this image in to the official profile image table. Are there any sakai.properties to check if this is the preferred configuration?

In the future though, insitutional profile images will need to be configured slightly differently, as outlined in the config here:
https://confluence.sakaiproject.org/display/PROFILE/Profile2

cheers,
s


On 21/01/2011, at 8:51 PM, David Horwitz wrote:

> Hi Steve,
> 
> The picture storage is used for institutional Id photos - so its something a little different from a profile picture. Certain tools like roster need to be able to display them whatever the user has selected as their photo. Traditionally though the profile tool allowed the user to select their id picture as their profile one.
> 
> D
> 
> On 01/21/2011 03:43 AM, Steve Swinsburg wrote:
>> 
>> Hi Bryan,
>> 
>> Profile2 doesn't support the FileSystemPhotoService, I wasn't aware it was being used - I was only aware of the db photo service where the images are stored in the JPEG_PHOTO column in SAKAI_PERSON_T. There is a conversion for the db file service to convert them to Profile2 photos. There are probably others in your situation so I'll JIRA this and see if we can get it implemented as a conversion. 
>> 
>> For Sakai 2.8 and later there is official image support via an entry in a database table that can link to external images, or the images can come from an LDAP attribute.
>> 
>> Can you send through the screenshot that you mention in your last message? I think I've also seen what you are seeing, but the image didn't come through.
>> 
>> Finally, the roster integration for profile2 is activated by this property:
>> 
>>  # Set this to tell the ProfileManager to get it's data from Profile2.
>> # If left unset, any tools that use the ProfileManager from the original profile tool (ie Roster)
>> # will continue to use the data from org.sakaiproject.api.app.profile.LegacyProfileManager.
>> # So you must set this to enable the integrations.
>> # If you are using a version of Sakai prior to 2.7, you need to apply the patch attached to
>> # http://jira.sakaiproject.org/browse/SAK-17573 in order for this property to have any effect
>> profile.manager.integration.bean=org.sakaiproject.profile2.legacy.ProfileManager
>> 
>> regards,
>> Steve
>> 
>> 
>> On 21/01/2011, at 12:33 PM, Bryan Bakotich wrote:
>> 
>>> Hi all,
>>> 
>>> In our current Sakai 2.6 production instance we use profile1 and the FileSystemPhotoService to integrate official photos into the Roster tool.
>>> 
>>> In our Sakai 2.7 dev instance there are no images showing up in the Roster tool (images from profile or official photos). I added the profile2 tool to my user account so that I now have a profile with image in both profile1 and profile2 and still no image shows up for my profile picture in the Roster tool. What profile tool is the Roster looking at in Sakai 2.7? And usually when there is no photo there is an image saying no photo exists for each user. Now there is just a grey bar (see screenshot).
>>> 
>>> So I guess I have two questions. What profile tool should I be using and how do I get the profile photo to show up in the Roster tool. What is the recommended way to get official photos into the Roster tool in Sakai 2.7? For the latter question it seems like I would have to download the profile1 code and make the same changes that I did to achieve this in Sakai 2.6, but I didn't know if there was a better way to do this with profile2.
>>> 
>>> -Bryan
>>> 
>>> -- 
>>> Bryan Bakotich
>>> Open Source Implementation Specialist
>>> Digital Media Center, Information & Technology Services
>>> Pacific Lutheran University
>>> Tacoma, WA 98447-0013
>>> Phone: 253-536-5021
>>> _______________________________________________
>>> 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"
>> 
>> 
>> _______________________________________________
>> 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"
> _______________________________________________
> 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"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110122/2d4e3685/attachment.html 


More information about the sakai-dev mailing list