...
- Are there any conversions, migrations or other administrative preparations required in order to start using the tool?
There is a conversion utility to convert out the image stored in the database table into ContentHosting for use in Profile2. This is not essential to run, people will just need to upload their image if they had one. Images in the original Profile tool were near impossible to add by a user unless they already had one uploaded somewhere so this might not be an issue. Existing institutional photos are not yet supported. No.
- Is there required configuration or does it work out of the box?
There are a number of sakai.properties you can use to control Profile2 at an installation level, none are essential though. See Confluence for the list All the configuration settings are optional and the tool is ready to work out of the box.
- Can complex or objectionable features be disabled?
Yes, almost everything can be locked down or disabled if you desire. Again, see Confluence for the list of properties. For items that cannot currently be disabled/locked, they soon will be able to be controlled in this way All configurable in sakai.properties. The tool Confluence page has a dedicated page with all configuration details.
- Does this tool depend on a file storage mechanism other than Content Hosting?
No.
- Are there any special requirements for deploying this project in a cluster? For example, does this project assume JGroups, shared network storage, UDP multicasting, or Terracotta server.
No. It has been verified as working OK on a cluster environment - actually, we (UFP) run it in a cluster.
- Was load testing performed? What were the results? Is a load testing report available?
No formal load testing however test were performed on 4000 dummy user accounts, performing searches and adding people as friends, load results and memory use was fine. There is a Jira ticket to allow Profiles to be searched via the Sakai Search ,this will improve search results even further. Note that his will be limited to Profile2 search since there are Privacy filters that need to be employed depending on who you are and what info you can see about a person. I had performed some load test for code optimization a long time ago on the 1.x versions - however, I currently don't have any useful information about it. David Roldan Martinez had also run some load tests with SiteStats afterwards which revealed some performance increase.
It would be excellent if we can have some kind of automatic load testing procedures (fired my Maven?) in the future.
- Are there features that are database intensive, either in terms of large data or heavy CPU demand?
Not that I am aware of The event aggregation mechanism needs to update value on SiteStats tables which can be, in some configurations, some kind heavy. There are two operational behaviors options regarding this: a real-time event aggregation thread (for small-medium sized installations) and a quartz job for event aggregation to be scheduled at will (for large sized installations).
Interoperability:
- Does any other Sakai tool or service depend on this functionality?
Roster depends on the legacy ProfileManager which is being pulled into Profile2 to give it it's data Not that I am aware of. There is currently (since Sakai 2.6.0) an Entity Broker capability that allows tools to self-register with sitestats, optionally providing event translations - this is made with a dependency on Entity Broker and none on SiteStats.
- Are there overlaps in functionality with other tools or services? Overlaps with standard Profile although with a richer feature set and improved interface
No.
- Is content created within sites? If so, are archive, import, search and duplicate features implemented?
No, the content is per user. Search is built in to Profile2 and import/export is already in Jira as a task Since version 2.0 there are per site reports. This data that can be imported/exported between sites. Archive is not implemented yet. Duplicate feature is available within the tool.
- Are there any data feeds (RSS, XML, JSON) exposed via the Entity broker, sdata, or a one-off implementation?
Yes, see EntityBroker support for Profile2 Currently not, but it is something that will implemented in the future.
- Does the work implement particular notable standards?
No. But the import/export will.