With Profile2 you can post updates (integrated with Twitter), search for people with common interests, view their profiles, view their connections, add them as a connection, send private messages, upload and share pictures, and much more.
Profile2 can be run seamlessly alongside the existing profile in Sakai to allow you to evaluate both profile tools. If you've never used the profile tool in Sakai before, now is the time to start.
The development of Profile2 started as part of an ESRC e-Social Science award at Lancaster University in 2008.
See it in action
See the presentation from the 2010 Sakai conference in Denver: Profile2 - Social networking for Sakai 2
The latest version in the 1.4 series (requires Sakai 2.8+) is:
1.4.6 released 23rd January 2011 (changelog)
The latest version in the 1.3 series (Sakai 2.4 onwards) is:
1.3.18 released 9th September 2011 (changelog) (Note that there was no 1.3.16 or 1.3.17 release)
Previous releases in the 1.4 series:
1.4.5 released 21st November 2011 (changelog) (release announcement) (Note that there was no official 1.4.4 release)
1.4.3 released 30th September 2011 (changelog) (release announcement)
1.4.2, released 11th August 2011 (changelog) (Note that there was no 1.4.1 release)
1.4.0, released 12th April 2011 (changelog)
1.3.15 released 11th April 2011 (changelog) (release announcement)
1.3.14 released 28th February 2011 (changelog) (release announcement)
1.3.13, released 22nd October 2010 (changelog)
1.3.12, released 25th August 2010 (changelog) (release announcement)
1.3.11, released 20th August 2010 (changelog) (release announcement)
1.3.10, released 12th August 2010 (changelog) (release announcement)
1.3.9, released 9th July 2010 (changelog) (release announcement)
1.3.8, released 24th May 2010 (changelog)
1.3.7, released 27th April 2010 (changelog)
1.3.6, released 25th March 2010 (changelog)
1.3.5, released 4th March 2010 (changelog)
1.3.4, released 6th January 2010 (changelog)
1.3.3, released 19th December 2009 (changelog)
1.3.2, released 18th December 2009 (changelog)
1.3.1, released 18th December 2009 (changelog)
1.3.0, released 18th December 2009 (changelog)
1.2.1, released 12th August 2009 (changelog)
1.2, released 17th July 2009 (changelog)
1.1, released 6th April 2009 (changelog)
1.0.1, released 6th February 2009 (changelog)
1.0, released 4th February 2009
There are no current experimental releases. To see what is coming in 1.5, checkout the nightly build server: http://nightly2.sakaiproject.org:8082/portal
Want to try it out first?
Profile2 is the default Profile in Sakai 2.7 and up, but you can also try it out now on the following servers:
- Latest stable version: http://nightly2.sakaiproject.org:8082/portal
- Latest development version: http://nightly2.sakaiproject.org:8085/portal
Both are hosted by the Sakai Foundation and are reset every 4 hours and 2.30am respectively, Eastern US time.
1. 1.3.x is compatible with all versions of Sakai, is bundled in Sakai 2.7 and has demonstrated production experience with Sakai 2.6, however lacks some of the newer features and improvements. Note that as of Sakai 2.9, this version is longer actively supported. Security fixes may be applied but it is recommend that you upgrade.
2. 1.4.x and later depend on the ActivityService API, which is only present in Kernel 1.2.0, therefore the minimum version of Sakai required is Sakai 2.8.
3. 1.5.x is the version that ships with Sakai 2.9.0+
4. 1.6.x is the current development version.
How to get it
Check one of the following Installation Guides that is appropriate for your particular version of Sakai. This will walk you through getting the Profile2 source code and its dependencies, and then building it.
Once you've built Profile2, continue on with the section below.
Upgrading from an older version?
You must make sure that you perform any necessary database conversion BEFORE you start Profile2, or you may run into problems later. Run the appropriate database conversion sql script found at:
PROFILE2-SRC/docs/database/<your db vendor>/
Also double check that you have removed the older version from Tomcat. Generally you only need to check TOMCAT/shared/lib to make sure that there are no suplicates of the profile2-api jars. Only the latest one should be in there. The other artifacts that are deployed to 'components' and 'webapps' should be updated automatically and no duplicates should exist.
Startup Sakai with auto.ddl=true in your Sakai properties as various new tables need to be created. If you cannot startup with this setting enabled, you will need to manually run the DB scripts located at:
PROFILE2-SRC/docs/database/<your db vendor>/
If you are creating the database tables for the first time, you want the appropriate profile2-ddl-....sql* (not the upgrades) for your version of Profile2.
Setting up Profile2 on MySQL?
Even if you are using auto.ddl=true for your database creation you should run the index-only sql scripts to generate the indexes on the various tables that Profile2 creates. Hibernate doesn't respect the index settings in the configuration files for MySQL, so the indexes aren't created. The index scripts are in the same directory as the creation/upgrade scripts above.
Once you've started up Sakai you'll be able to add the new Profile2 tool to My Workspace sites.
IMPORTANT See below for the sakai.properties you can use to configure Profile2 on a global level as well as the additional JAVA_OPTS you might need if you are behind a firewall/proxy.
Profile2 uses the following sakai.properties:
Profile2 has a built-in Twitter integration for status updates. This is configurable by each user in their Preferences page of their Profile (not to be confused with the main Account Preferences). Once a user has linked their Twitter account, status updates will then update Twitter. Administrators can control this globally by adjusting the profile2.integration.twitter.enabled sakai property.
If you are behind a proxy or web cache, you will need to add these settings to your JAVA_OPTS to allow Profile2 to send status updates to Twitter:
NOTE: http.proxyUser and http.proxyPassword are only required if you need to authenticate to your proxy.
Changing the Twitter source (optional)
By default, Twitter updates will appear to come from Profile2 (as Profile2 is a registered Twitter application).
If you want updates to come from a different 'source', you need to register an application with Twitter and provide the settings to Profile2. Fill out this form: http://twitter.com/oauth_clients/new
Be sure to choose 'client' as the Application type, NOT 'browser'. When user's link their account they will be prompted to enter a code into Profile2, that will then be verified and their own access token and secret stored in the database.
Once you have filled out the form, add the key and secret supplied to your application in the following sakai.properties:
DO NOT reset these keys without updating the properties in Sakai, as the integration will no longer function if they are out of sync (they are essentially your application's username and password).
Give Profile2 an icon in the tool list
Add this to SAKAI-SRC/reference/library/src/webapp/skin/YOURSKIN/portal.css
See this page for information about the Entities exposed/supported by Profile2.
See this page for a list of institutions using or trialling Profile2
Found a bug? Want something added? Things don't look right?
Check the Common issues with Profile2 page.
If that doesn't help, then please submit all bugs and feature requests as Jira tickets at:http://jira.sakaiproject.org/jira/browse/PRFL
If the issue is cosmetic, please make sure to include what environment (operating system and browser + version) you experienced the issue on.
Profile2 currently supports the following languages:
- English (British and Australian) - default
- English (en_US)
- Catalan (ca)
- Spanish (es)
- Dutch (nl)
- Portuguese (pt_PT)
- Russian (ru)
- Indonesian (in_ID)
- Japanese (ja)
If you would like Profile2 to appear in your language, feel free to translate the following three property files and send them along:
In addition, the email templates can be internationalised:
Please append the country code/variant to the filename: (eg template-connectionRequest_en_GB.xml)
Showing the first 100 issues - view full list.