Same as feedapi_mapper.module maps to cck fields, taxonomies and node fields; user information from/to Dokeos might be.

Then we can add a user profile tab called "Dokeos", with fields: Official code, Surname and Name.

Optionally, tab "Dokeos" would be read-only and previous fields appear into a fieldset of account edit form.

Blessings!

Comments

develcuy’s picture

develcuy commented

Forgot to mention that profile.module will dead on September 1, so CCK integration will save us time :)

develcuy’s picture

develcuy commented

This should go to Version 2.0 but is not that early. So I'm starting to work on integration with content_profile.module.

develcuy’s picture

develcuy commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
Assigned: Unassigned » develcuy

Implement it with native core stuff is better, so I'm moving it to Drupal 7 :)

develcuy’s picture

develcuy commented
Project: Dokeos Integration » Chamilo integration
Version: 7.x-2.x-dev » 7.x-1.x-dev
ywarnier’s picture

ywarnier commented

There is a way, in Chamilo, to define "extra" user fields (country, birth date, department, city, etc). These fields could also be recovered from the Chamilo installation through web services.

The available fields for users (at this time) are:

  • lastname
  • firstname
  • e-mail
  • chamilo status (role)
  • official code
  • user picture url
  • competences (textarea)
  • diplomas
  • openarea
  • teach
  • productions
  • language
  • registration date
  • expiration date
  • status (active/inactive)
  • openid
  • preferred theme
develcuy’s picture

develcuy commented
Title: Dokeos user information mapper » Chamilo user information mapper