Index: openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html 20 Oct 2003 15:44:31 -0000 1.2 +++ openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html 19 Feb 2004 14:59:42 -0000 1.3 @@ -1,12 +1,12 @@ -IMS Sync driver design
Prev Design

IMS Sync driver design

- by Lars Pind
+IMS Sync driver design

Alex logo
Prev Design

IMS Sync driver design

+ by Lars Pind OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

TODO

We need examples of how the communication would be done from our +

TODO

We need examples of how the communication would be done from our clients.

The "GetDocument" communications service contract could be a generic system-wide service contract.

We might need a source/ID column in the users table to identify where they're imported from for doing updates, particularly if -importing from multiple sources (or when some users are local.)

Execution Story

  1. We will parse a document in the IMS Enterprise +importing from multiple sources (or when some users are local.)

Execution Story

  1. We will parse a document in the IMS Enterprise Specification format (example XML document), and translate it into calls to the batch user sync API.

  2. The document will contain either the complete user listitemst (IMS: @@ -135,7 +135,7 @@ <photo imgtype="gif"><extref>...</extref></photo> if present: HTTP GET the photo, insert it into the system. (Do we do this, then, with all users when doing a snapshot update?) -

Resources

Resources