outlook2ldap/libs/Torus.README.html

<HTML>
<HEAD>
<TITLE>Torus</TITLE>
<LINK REV="made" HREF="mailto:">
</HEAD>

<BODY>

<A NAME="__index__"></A>
<!-- INDEX BEGIN -->

<UL>

        <LI><A HREF="#name">NAME</A></LI>
        <LI><A HREF="#description">DESCRIPTION</A></LI>
        <LI><A HREF="#news">NEWS</A></LI>
        <UL>

                <UL>

                        <UL>

                                <LI><A HREF="#20030118  initial checkin">2003-01-18  -  initial check-in</A></LI>
                        </UL>

                </UL>

        </UL>

        <LI><A HREF="#requirements">REQUIREMENTS</A></LI>
        <LI><A HREF="#authors / copyright">AUTHORS / COPYRIGHT</A></LI>
        <LI><A HREF="#contributors">CONTRIBUTORS</A></LI>
        <LI><A HREF="#support / warranty">SUPPORT / WARRANTY</A></LI>
        <LI><A HREF="#bugs">BUGS</A></LI>
        <LI><A HREF="#todoshowstopper">TODO-SHOWSTOPPER</A></LI>
        <LI><A HREF="#todo">TODO</A></LI>
        <LI><A HREF="#ideas">IDEAS</A></LI>
</UL>
<!-- INDEX END -->

<HR>
<P>
<HR>
<H1><A NAME="name">NAME</A></H1>
<P>Torus</P>
<P>
<HR>
<H1><A NAME="description">DESCRIPTION</A></H1>
<PRE>
  Torus is a module to ease migration from Outlook.</PRE>
<PRE>
  Torus uses CPAN's Win32::OLE to access Microsoft's MAPI locally and 
  CPAN's Net::LDAP to connect to a remote OpenLDAP-server (slapd).</PRE>
<PRE>
  Access to these storage-implementations is wrapped via Data::Storage.
  Core functionality of Torus is currently provided from Data::Transfer::Sync.</PRE>
<PRE>
  We are starting with Contacts/Adresses, will go along with Messages, 
  Calendar-Items and Journaling-Features.
  The &quot;rest&quot; should be able to be modeled and implemented on top of this.</PRE>
<PRE>
  This is more a reference implementation than anything actually useful.  ;-)
  You'll also like to take a look at:
    - Kroupware Project: <A HREF="http://kroupware.kde.org">http://kroupware.kde.org</A>
    - Outlook Connector Project: <A HREF="http://otlkcon.sourceforge.net">http://otlkcon.sourceforge.net</A>
    - bynari InsightConnector: <A HREF="http://bynari.net/index.php?id=7">http://bynari.net/index.php?id=7</A></PRE>
<P>
<HR>
<H1><A NAME="news">NEWS</A></H1>
<P>
<H4><A NAME="20030118  initial checkin">2003-01-18  -  initial check-in</A></H4>
<P>
<HR>
<H1><A NAME="requirements">REQUIREMENTS</A></H1>
<PRE>
  Win32::OLE
  Net::LDAP
  Data::Storage
  Data::Transfer::Sync
    ... and all their dependencies</PRE>
<P>
<HR>
<H1><A NAME="authors / copyright">AUTHORS / COPYRIGHT</A></H1>
<PRE>
  The Data::Storage module is Copyright (c) 2002 Andreas Motl.
  All rights reserved.</PRE>
<PRE>
  You may distribute it under the terms of either the GNU General Public
  License or the Artistic License, as specified in the Perl README file.</PRE>
<P>
<HR>
<H1><A NAME="contributors">CONTRIBUTORS</A></H1>
<PRE>
  Jan Hoffmann &lt;jan@romain-volk.com&gt;
  Sebastian Utz &lt;s.utz@tunemedia.de&gt;</PRE>
<P>
<HR>
<H1><A NAME="support / warranty">SUPPORT / WARRANTY</A></H1>
<PRE>
  Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</PRE>
<P>
<HR>
<H1><A NAME="bugs">BUGS</A></H1>
<P>
<HR>
<H1><A NAME="todoshowstopper">TODO-SHOWSTOPPER</A></H1>
<PRE>
  o sync items from ldap back to outlook</PRE>
<P>
<HR>
<H1><A NAME="todo">TODO</A></H1>
<PRE>
  - outlook2ldap - essential modules:
    - Net::LDAP
      - Convert::ASN1 / BER1
    - Unicode::String
      - MIME::Base64
    o use setup.pm with autoinstall, use ExtUtils::MakeMaker and/or h2xs
  o enhance mapping through expressions
    o provide multiple use of same fields
    o provide mechanism to concatenate fields
    --&gt; see etc/_future!
  o make integrated setup
  o provide gui(s)
    o development (create mappings and stuff (testing, ...))
    o productive use (control sync-processing at a central console)
    o little hotsync-button (iconbar bottom-right) which provides some actions and some configuration-settings (put ACLs on these settings?)
  o move libs/Torus to nfo-modules, exclude various metadata needed to actually sync with ldap and mappings (csv-files)
  o provide example to sync with mysql/Tangram/mbox/...
  o integrate genSchema.pl
    o regeln:
      o 3.spalte in outlook_ole_fields.csv: für &quot;genSchema.pl&quot;
      o wenn 2.spalte und/oder 3. leer, dann wird kein mapping gemacht (genSchema sowieso nicht)
    --&gt; see etc/_future!
  o daten &quot;rückwärts&quot; übertragen!
  o mapping aufbohren (csv -&gt; xml) - integrate &quot;schema&quot;-property _per-field_!!!
    o have the engine use this
    o maybe provide cross-checks
    --&gt; see etc/_future!
  o transfer statistics
  o zugriff auf outlook (2002) ohne rückfrage gewähren?
    o v.a. wichtig, wenn integrierter zugriff (z.b. durch outlook-plugin) stattfindet
  + verwenden _aller_ attribute, die mit einem address-eintrag assoziiert sein können?
     + mileage (reisekilometer) kommt!
     + bis dato unbekannte mapi-felder sollten nun auch verwendet werden können
  o declare folder-mapping inside xml-file
  o check-before-delete doesn't seem to work (again!)
  o make basedn configurable
    o introduce host-to-basedn-mapping
    o provide additional fallback basedn
  o maybe additional permissions for folder-autocreation
  o rework regexes in Torus::Driver::ldap
  o spaces in ou's?
  o utf8-encoding for dn's in ou's
    o also in other property-names (besides the attributes)?!
    o ä, ö, ü
  o Insight:
    o cclient.dll
    o InsightConnector.dll
  o folder-mapping
    o leerzeichen (non-word-chars) do not work inside foldernames
    o regex fails:
    o introduce some &quot;highlevel-splitting&quot; of ldap-addresses
  o fix problems occoured 2003-01-06/07 @barschwaechter: rules, access to mapi, etc. (see email)
  o do a _true_ sync! (no delete/add)
  o handle folder-mapping/-creation completely _before_ continuing with single entries
    o create non-existant and stuff....
  o timestamp log-entries
  o add fieldname-context to ldap_errors.log
  o regeln für cn/dn - build
    o wenn &quot;sn&quot; gesetzt, dann nimm &quot;sn&quot; als &quot;cn&quot;
    o wenn &quot;givenname&quot; gesetzt, dann füge zu &quot;cn&quot; hinzu (bisheriger &quot;build&quot;-Vorgang)
    o wenn &quot;sn&quot; leer, dann nimm stattdessen &quot;FileAs&quot; als &quot;cn&quot; und ab [Debug Level=1]info 
    o wenn &quot;FileAs&quot; leer, dann nimm stattdessen &quot;FirstName&quot; und ab [Debug Level=1]info 
    o wenn &quot;FirstName&quot; leer, dann nimm stattdessen &quot;CompanyName&quot; und ab [Debug Level=1]info
    else ab [Debug Level=1] Warn: 
    &quot;Couldn't build DN/CN cause neighter SN/FileAs/FirstName/CompanyName does exist.&quot; (Should not happen).
    o collision checks!!!
  o convert date-fields
  o detect must-not-have characters in dn:
    + replace &quot;+&quot; through &quot;&amp;&quot;
    o replace &quot;,&quot; through &quot;&quot; [Kill]
    o replace &quot;ô&quot; through &quot;&quot; [to UTF8]
  o enhance mechanisms to talk to OLE:
    o use &quot;-&gt;EnumAllObjects&quot;
    o use &quot;-&gt;FreeUnusedLibraries&quot;
    o use &quot;-&gt;LastError&quot;
  o encode &quot;dn&quot; with utf8
  o &quot;member&quot; is empty!!!
  o free resources while processing
    o Outlook (OLE)
    o Perl (Variables, Objects)
    o LDAP-Server (Handle)
</PRE>
<PRE>

  o for Horde:
    o helper: some kinda &quot;genSchema.pl&quot;
    o app: LDAP-Browser</PRE>
<PRE>
  o split 'syncOutlookContacts.ini' into 'torus.ini' and 'outlook2ldap.ini'
  o 'syncOutlookContacts.pl' reads 'outlook2ldap.ini' and runs 'feed.pl'
</PRE>
<PRE>

  o check howto handle outlook-profile logon
  o mode to transfer all items in bunch
  o use a news- (nntp) server to (maybe) mimic journalling-functionality</PRE>
<P>
<HR>
<H1><A NAME="ideas">IDEAS</A></H1>
<PRE>
  o acl based permissions (use Data::ACL?)
  o combine Torus::Xyz with Device::Xyz somehow?
  o assure published stuff contains no client-specific informations (HMI, ...)
  o CPAN's AppConfig is still needed for now (could this be changed? e.g. using App::Config?)
    o if not, just include it below &quot;libs&quot; or install &quot;nmake&quot; (through integrated setup) before configuring CPAN
      (if you already have, do &quot;perl -MCPAN -eshell&quot; and &quot;o conf init&quot; to redo configuration)
  o rework folder-mapping to use xml
  o rework field-mapping to use xml (Data::Transfer::Sync!)
  o rework declaration of while-transfer-rules and after-transfer-patches to xml
    o example of a &quot;while-transfer-rule&quot;
      o build &quot;dn&quot; from &quot;cn/sn&quot;
      o must have &quot;sn&quot;
      o if no &quot;sn&quot; given, just use &quot;Vorname&quot;
      o don't allow some special characters inside &quot;dn&quot;: '+' seems to get translated to '&amp;' at somewhere in code
    o example of a &quot;after-transfer-patch-rule&quot;
      o copy contents of field &quot;x&quot; to field &quot;y&quot; to nivelate(?) access from ldap-query-engines we don't have access to! (the source!)
        (e.g. query-/search-engines in commercial products like &quot;MS Outlook 2000|2002|Express&quot;,
        which also don't have _any_ mechanism to parametrize them)
  o write papers about networking (computers _and_ small/embedded/electronic devices (atmel, c-control))
     o janosch: how to control arbitrary devices via personal computers _and_ standalone circuits in parallel!
        (using Device::SerialPort and Conrad C-Control together)
  o implement infrastructure(s)
  o actually handle folders (check, autocreation) completely _before_ starting to sync/process items/entries!
  o provide easy-to-access shell-interface to LDAP (e.g. via Xyz::Xyz or (maybe later) &quot;oedit.pl&quot;)
    o this removes the need for the currently used Java-based Ldap-Client (which will stay more comfortable - of course)
    o navigate via &quot;cd&quot; through containers, show items/entries via (e.g.) &quot;dump&quot;(?) and stuff...
      ... the interactive feeling/behaviour is similar to navigating in a filesystem via a commandline-interface (CLI)
  o sum up &quot;must-have&quot; features of known synchronization-tools for (e.g.) ...
  o use news (the nntp-protocol) for journalling-functionality
  o have mapping stored inside ldap as well</PRE>

</BODY>

</HTML>
1	joko	1.1	<HTML>
2			<HEAD>
3			<TITLE>Torus</TITLE>
4			<LINK REV="made" HREF="mailto:">
5			</HEAD>
6
7			<BODY>
8
9			<A NAME="__index__"></A>
10			<!-- INDEX BEGIN -->
11
12			<UL>
13
14			<LI><A HREF="#name">NAME</A></LI>
15			<LI><A HREF="#description">DESCRIPTION</A></LI>
16			<LI><A HREF="#news">NEWS</A></LI>
17			<UL>
18
19			<UL>
20
21			<UL>
22
23			<LI><A HREF="#20030118 initial checkin">2003-01-18 - initial check-in</A></LI>
24			</UL>
25
26			</UL>
27
28			</UL>
29
30			<LI><A HREF="#requirements">REQUIREMENTS</A></LI>
31			<LI><A HREF="#authors / copyright">AUTHORS / COPYRIGHT</A></LI>
32			<LI><A HREF="#contributors">CONTRIBUTORS</A></LI>
33			<LI><A HREF="#support / warranty">SUPPORT / WARRANTY</A></LI>
34			<LI><A HREF="#bugs">BUGS</A></LI>
35	joko	1.3	<LI><A HREF="#todoshowstopper">TODO-SHOWSTOPPER</A></LI>
36	joko	1.1	<LI><A HREF="#todo">TODO</A></LI>
37			<LI><A HREF="#ideas">IDEAS</A></LI>
38			</UL>
39			<!-- INDEX END -->
40
41			<HR>
42			<P>
43			<HR>
44			<H1><A NAME="name">NAME</A></H1>
45			<P>Torus</P>
46			<P>
47			<HR>
48			<H1><A NAME="description">DESCRIPTION</A></H1>
49			<PRE>
50			Torus is a module to ease migration from Outlook.</PRE>
51			<PRE>
52			Torus uses CPAN's Win32::OLE to access Microsoft's MAPI locally and
53			CPAN's Net::LDAP to connect to a remote OpenLDAP-server (slapd).</PRE>
54			<PRE>
55			Access to these storage-implementations is wrapped via Data::Storage.
56			Core functionality of Torus is currently provided from Data::Transfer::Sync.</PRE>
57			<PRE>
58			We are starting with Contacts/Adresses, will go along with Messages,
59			Calendar-Items and Journaling-Features.
60			The "rest" should be able to be modeled and implemented on top of this.</PRE>
61			<PRE>
62			This is more a reference implementation than anything actually useful. ;-)
63			You'll also like to take a look at:
64			- Kroupware Project: <A HREF="http://kroupware.kde.org">http://kroupware.kde.org</A>
65			- Outlook Connector Project: <A HREF="http://otlkcon.sourceforge.net">http://otlkcon.sourceforge.net</A>
66			- bynari InsightConnector: <A HREF="http://bynari.net/index.php?id=7">http://bynari.net/index.php?id=7</A></PRE>
67			<P>
68			<HR>
69			<H1><A NAME="news">NEWS</A></H1>
70			<P>
71			<H4><A NAME="20030118 initial checkin">2003-01-18 - initial check-in</A></H4>
72			<P>
73			<HR>
74			<H1><A NAME="requirements">REQUIREMENTS</A></H1>
75			<PRE>
76			Win32::OLE
77			Net::LDAP
78			Data::Storage
79			Data::Transfer::Sync
80			... and all their dependencies</PRE>
81			<P>
82			<HR>
83			<H1><A NAME="authors / copyright">AUTHORS / COPYRIGHT</A></H1>
84			<PRE>
85			The Data::Storage module is Copyright (c) 2002 Andreas Motl.
86			All rights reserved.</PRE>
87			<PRE>
88			You may distribute it under the terms of either the GNU General Public
89			License or the Artistic License, as specified in the Perl README file.</PRE>
90			<P>
91			<HR>
92			<H1><A NAME="contributors">CONTRIBUTORS</A></H1>
93			<PRE>
94			Jan Hoffmann <jan@romain-volk.com>
95			Sebastian Utz <s.utz@tunemedia.de></PRE>
96			<P>
97			<HR>
98			<H1><A NAME="support / warranty">SUPPORT / WARRANTY</A></H1>
99			<PRE>
100			Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</PRE>
101			<P>
102			<HR>
103			<H1><A NAME="bugs">BUGS</A></H1>
104			<P>
105			<HR>
106	joko	1.3	<H1><A NAME="todoshowstopper">TODO-SHOWSTOPPER</A></H1>
107			<PRE>
108			o sync items from ldap back to outlook</PRE>
109			<P>
110			<HR>
111	joko	1.1	<H1><A NAME="todo">TODO</A></H1>
112			<PRE>
113			- outlook2ldap - essential modules:
114			- Net::LDAP
115			- Convert::ASN1 / BER1
116			- Unicode::String
117			- MIME::Base64
118			o use setup.pm with autoinstall, use ExtUtils::MakeMaker and/or h2xs
119			o enhance mapping through expressions
120			o provide multiple use of same fields
121			o provide mechanism to concatenate fields
122			--> see etc/_future!
123			o make integrated setup
124			o provide gui(s)
125			o development (create mappings and stuff (testing, ...))
126			o productive use (control sync-processing at a central console)
127			o little hotsync-button (iconbar bottom-right) which provides some actions and some configuration-settings (put ACLs on these settings?)
128			o move libs/Torus to nfo-modules, exclude various metadata needed to actually sync with ldap and mappings (csv-files)
129			o provide example to sync with mysql/Tangram/mbox/...
130			o integrate genSchema.pl
131			o regeln:
132			o 3.spalte in outlook_ole_fields.csv: für "genSchema.pl"
133			o wenn 2.spalte und/oder 3. leer, dann wird kein mapping gemacht (genSchema sowieso nicht)
134			--> see etc/_future!
135			o daten "rückwärts" übertragen!
136			o mapping aufbohren (csv -> xml) - integrate "schema"-property _per-field_!!!
137			o have the engine use this
138			o maybe provide cross-checks
139			--> see etc/_future!
140			o transfer statistics
141	joko	1.2	o zugriff auf outlook (2002) ohne rückfrage gewähren?
142	joko	1.1	o v.a. wichtig, wenn integrierter zugriff (z.b. durch outlook-plugin) stattfindet
143			+ verwenden _aller_ attribute, die mit einem address-eintrag assoziiert sein können?
144			+ mileage (reisekilometer) kommt!
145			+ bis dato unbekannte mapi-felder sollten nun auch verwendet werden können
146			o declare folder-mapping inside xml-file
147			o check-before-delete doesn't seem to work (again!)
148			o make basedn configurable
149			o introduce host-to-basedn-mapping
150			o provide additional fallback basedn
151			o maybe additional permissions for folder-autocreation
152			o rework regexes in Torus::Driver::ldap
153			o spaces in ou's?
154			o utf8-encoding for dn's in ou's
155			o also in other property-names (besides the attributes)?!
156			o ä, ö, ü
157			o Insight:
158			o cclient.dll
159			o InsightConnector.dll
160			o folder-mapping
161			o leerzeichen (non-word-chars) do not work inside foldernames
162			o regex fails:
163			o introduce some "highlevel-splitting" of ldap-addresses
164			o fix problems occoured 2003-01-06/07 @barschwaechter: rules, access to mapi, etc. (see email)
165			o do a _true_ sync! (no delete/add)
166			o handle folder-mapping/-creation completely _before_ continuing with single entries
167			o create non-existant and stuff....
168			o timestamp log-entries
169			o add fieldname-context to ldap_errors.log
170			o regeln für cn/dn - build
171			o wenn "sn" gesetzt, dann nimm "sn" als "cn"
172			o wenn "givenname" gesetzt, dann füge zu "cn" hinzu (bisheriger "build"-Vorgang)
173			o wenn "sn" leer, dann nimm stattdessen "FileAs" als "cn" und ab [Debug Level=1]info
174			o wenn "FileAs" leer, dann nimm stattdessen "FirstName" und ab [Debug Level=1]info
175			o wenn "FirstName" leer, dann nimm stattdessen "CompanyName" und ab [Debug Level=1]info
176			else ab [Debug Level=1] Warn:
177			"Couldn't build DN/CN cause neighter SN/FileAs/FirstName/CompanyName does exist." (Should not happen).
178			o collision checks!!!
179			o convert date-fields
180			o detect must-not-have characters in dn:
181			+ replace "+" through "&"
182			o replace "," through "" [Kill]
183			o replace "ô" through "" [to UTF8]
184			o enhance mechanisms to talk to OLE:
185			o use "->EnumAllObjects"
186			o use "->FreeUnusedLibraries"
187			o use "->LastError"
188			o encode "dn" with utf8
189			o "member" is empty!!!
190			o free resources while processing
191			o Outlook (OLE)
192			o Perl (Variables, Objects)
193			o LDAP-Server (Handle)
194			</PRE>
195			<PRE>
196
197			o for Horde:
198			o helper: some kinda "genSchema.pl"
199			o app: LDAP-Browser</PRE>
200	joko	1.2	<PRE>
201			o split 'syncOutlookContacts.ini' into 'torus.ini' and 'outlook2ldap.ini'
202	joko	1.3	o 'syncOutlookContacts.pl' reads 'outlook2ldap.ini' and runs 'feed.pl'
203			</PRE>
204			<PRE>
205
206			o check howto handle outlook-profile logon
207			o mode to transfer all items in bunch
208			o use a news- (nntp) server to (maybe) mimic journalling-functionality</PRE>
209	joko	1.1	<P>
210			<HR>
211			<H1><A NAME="ideas">IDEAS</A></H1>
212			<PRE>
213			o acl based permissions (use Data::ACL?)
214			o combine Torus::Xyz with Device::Xyz somehow?
215			o assure published stuff contains no client-specific informations (HMI, ...)
216			o CPAN's AppConfig is still needed for now (could this be changed? e.g. using App::Config?)
217			o if not, just include it below "libs" or install "nmake" (through integrated setup) before configuring CPAN
218			(if you already have, do "perl -MCPAN -eshell" and "o conf init" to redo configuration)
219			o rework folder-mapping to use xml
220			o rework field-mapping to use xml (Data::Transfer::Sync!)
221			o rework declaration of while-transfer-rules and after-transfer-patches to xml
222			o example of a "while-transfer-rule"
223			o build "dn" from "cn/sn"
224			o must have "sn"
225			o if no "sn" given, just use "Vorname"
226			o don't allow some special characters inside "dn": '+' seems to get translated to '&' at somewhere in code
227			o example of a "after-transfer-patch-rule"
228			o copy contents of field "x" to field "y" to nivelate(?) access from ldap-query-engines we don't have access to! (the source!)
229			(e.g. query-/search-engines in commercial products like "MS Outlook 2000\|2002\|Express",
230			which also don't have _any_ mechanism to parametrize them)
231			o write papers about networking (computers _and_ small/embedded/electronic devices (atmel, c-control))
232			o janosch: how to control arbitrary devices via personal computers _and_ standalone circuits in parallel!
233			(using Device::SerialPort and Conrad C-Control together)
234			o implement infrastructure(s)
235			o actually handle folders (check, autocreation) completely _before_ starting to sync/process items/entries!
236			o provide easy-to-access shell-interface to LDAP (e.g. via Xyz::Xyz or (maybe later) "oedit.pl")
237			o this removes the need for the currently used Java-based Ldap-Client (which will stay more comfortable - of course)
238			o navigate via "cd" through containers, show items/entries via (e.g.) "dump"(?) and stuff...
239			... the interactive feeling/behaviour is similar to navigating in a filesystem via a commandline-interface (CLI)
240			o sum up "must-have" features of known synchronization-tools for (e.g.) ...
241			o use news (the nntp-protocol) for journalling-functionality
242			o have mapping stored inside ldap as well</PRE>
243
244			</BODY>
245
246			</HTML>
MailToCvsAdmin">MailToCvsAdmin	ViewVC Help
Powered by ViewVC 1.1.26