[Building Sakai] Profile/Roster question

Steve Swinsburg steve.swinsburg at gmail.com
Fri Jan 21 23:34:30 PST 2011


Hi Bryan,

When you enable the official image support in Profile2 you have a suite of options available, including the data source, and the ability for users to select that image or one of their preference, or lock it down completely. This should cover all use cases. If you have a use case in mind but are not sure of the settings, let me know and I will provide the configuration for you.

If possible, when you go to 1.4, it might be worthwhile importing URLs to the student images into the PROFILE_IMAGES_OFFICIAL_T table. Otherwise we'll need to add additional support for reading the location of those images. when they might be best served as a URL (although you could JIRA that as a feature request and we could investigate)

cheers,
Steve

### OFFICIAL IMAGE SUPPORT

# To enable support for using official images, set to true:
profile2.official.image.enabled=false (true/false, default false)

# If enabled, where should Profile2 look for the officially provided images?
# If 'url', you need to add a URL for each user to the PROFILE_IMAGES_OFFICIAL_T table in the database.
# If 'provider', you need your UserDirectoryProvider implementation to add a BASE64 encoded image to a property
# on the User object. This is already in place for the LDAP provider, just setup the jpegPhoto attribute.
# See http://jira.sakaiproject.org/browse/SAK-17816.
profile2.official.image.source=url (url/provider, default url)

# If enabled and you set the source to 'provider' above you also need to specify the attribute,
# if different to this value.
profile2.official.image.attribute=jpegPhoto (default jpegPhoto)

# Note that if you want to use *only* officially provided images you also should set
# profile2.picture.type=official
# If you want to allow a user to choose either the official image or an uploaded/url one of their choice,
# do not set type=official and rather set profile2.picture.type=url/upload. They will then be able to choose
# to use either the official image, or one they select.
# Remember, you can always disable changes altogether via profile2.picture.change.enabled=false

https://confluence.sakaiproject.org/display/PROFILE/Profile2

On 22/01/2011, at 10:57 AM, Bryan Bakotich wrote:

> Steve,
> 
> I fixed the issue I was having in the last screenshot. I must've been tired yesterday because I didn't notice the big stack trace in the logs I was getting each time I tried to view the photos. We were experiencing the bug described here: https://jira.sakaiproject.org/browse/PRFL-425
> I upgraded from version 1.3.11 to 1.3.13 and that fixed the issue.
> 
> One weird thing about this is that the Roster was defaulting to use profile2 even without the sakai.property you showed me (profile.manager.integration.bean=org.sakaiproject.profile2.legacy.ProfileManager). I had to change this property to profile.manager.integration.bean=org.sakaiproject.api.app.profile.LegacyProfileManager so that the Roster tool would use profile1.
> 
> I don't think we actually need a conversion from FileSystemPhotoService to profile2 because it is our university policy that we are not aloud to automatically make an official photo a profile photo. This is something that the user has to manually choose to do (or select their own photo for their profile). Users are not aloud to change their official photo since it is used by professors to identify their students.
> 
> I am hoping that profile photo and official photo are kept separate in the 1.4 series of profile2. That way we can use profile2 the same way we use profile1 now. So for now I think we will go back to using profile1 with the FileSystemPhotoService. Let me know if you have any questions for me on our setup with official/profile pictures. Profile2 does look like a nice improvement to the old profile and we are hoping to use it if we can work in our requirements to keep official and profile pictures separate.
> 
> -Bryan
> 
> On Fri, Jan 21, 2011 at 8:49 AM, Bryan Bakotich <bakotibj at plu.edu> wrote:
> Steve,
> 
> Here's the screenshot.
> 
> -Bryan
> 
> 
> On Thu, Jan 20, 2011 at 5:43 PM, Steve Swinsburg <steve.swinsburg at gmail.com> 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"
> 
> 
> 
> 
> -- 
> Bryan Bakotich
> Open Source Implementation Specialist
> Digital Media Center, Information & Technology Services
> Pacific Lutheran University
> Tacoma, WA 98447-0013
> Phone: 253-536-5021
> 
> 
> 
> -- 
> Bryan Bakotich
> Open Source Implementation Specialist
> Digital Media Center, Information & Technology Services
> Pacific Lutheran University
> Tacoma, WA 98447-0013
> Phone: 253-536-5021

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


More information about the sakai-dev mailing list