Integration of Civicspaces + Moodle + Elgg + new Drupal modules.(without LDAP)
Moodle, Drupal, Civicrm, Civiclabs and Elgg working together with priority for Drupal as main framework.
Moodle, Civicrm, Elgg and Civiclabs working as modules at the Drupal with rich possibilities for customizing settings.
2.1. Moodle
integration (for example):
settings of Moodle in drupal/administer/modules.
Layout template (CSS) for Moodle and Drupal with keeping specific interface for Drupal and Moodle
Rebuilding user.module from drupal for some specific information from Moodle, for example: enrolled courses, pm, teacher or student, last login, information from Moodle/gradebook module etc.
One-sign on process (there is very simple one sign on module for drupal and moodle).
Without duplication of data from Moodle-profile and Drupal-profile, all that information automatically copied from Drupal-registration process.
Selecting some useful modules and blocks from Moodle repository for Academic use.
Etc.
2.2. Elgg
integration (There is Elgg as Moodle Module we need Elgg as
Drupal module).
Sharing information between Elgg, other blocks1 and Drupal.
Common layout/themes engine.
Look at the CATALYST
2.3. CivicSpace
...,
customization of some specific forms, for reuse.
Common layout/themes engine.
2.4. CivicCRM,
templates for academic society.
common layout/themes engine.
Sharing information from Moodle calendar and others.etc.
There is civicCrm for drupal as module.
2.5. Some new
modules for Drupal:
information about publications (based on customization of drupal/modules/forms from civicSpace)
some staff module showing information about staff of academic society for public.
New students - recruitment process of new students
Etc.
One installation process.
Sharing information between each block from databases (minimizing of duplication of data at the database)
Common update script and backup mechanism for all components (engines of each block and modules)
1block As block I understand: Moodle, Elgg, CivicSpace modules, CivicCRM