Unless your institute is aggressively ambitious, when deploying Sakai for the first time, it is sensible to keep the range of additional tools to a minimum. The more code you have, the more code you will need to verify, and the more configuration possibilities will exist. This minimalistic mentality ensures the greatest opportunity for stability and lowers the risks of random calls at random times for those poor administrators that are so very busy in the engine rooms shoveling coal.
Sometimes, the balance is difficult to find. Tools such as Evaluations tool, beg for deployment due to their wealth of enhanced pedagogically supportive functionality and wide-scale deployment by well-known universities around the world. Even under these circumstances, first test thoroughly before deployment. Bringing in the administrators early at this point increases their specific, tool-related skill levels before the noise of daily battle.
During the course of time, as administrators...