<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>LDIF Import/Export</title>
  <pubDate>Thu, 08 Jan 2009 14:46:08 -0500</pubDate>
  <link>http://bugs.horde.org/ticket/2506</link>
  <atom:link rel="self" type="application/rss+xml" title="LDIF Import/Export" href="http://bugs.horde.org/ticket/2506/rss" />
  <description>LDIF Import/Export</description>

  
  
  <item>
   <title>I would be wonderful if the Horde Address Book would be able</title>
   <description>I would be wonderful if the Horde Address Book would be able to import an LDIF file, like the kind Thunderbird will export for its address book. I believe such a feature would provide greater reliability in the importing of such information.

Of course, exporting to LDIF would be nice as well.</description>
   <pubDate>Wed, 24 Aug 2005 11:09:17 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t10763</link>
  </item>
  <item>
   <title>I support that one. It's a pain to import from csv. There ha</title>
   <description>I support that one. It's a pain to import from csv. There has to be a easier of getting a decent address book on the server (with phone numbers, addresses, web pages and so on). Thunderbird's address book exports in ldif, so it would be very useful to import that into turba.</description>
   <pubDate>Sun, 15 Jan 2006 21:53:17 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t15596</link>
  </item>
  <item>
   <title>Moving to the Turba queue (we may end up implementing this i</title>
   <description>Moving to the Turba queue (we may end up implementing this in the Horde_Data package, but even that would be Framework, not Horde Base. anyway logically it makes sense to me with Turba).</description>
   <pubDate>Fri, 24 Nov 2006 00:36:42 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t26599</link>
  </item>
  <item>
   <title>Some links and code for implementation pointers.

http://w</title>
   <description>Some links and code for implementation pointers.

http://www.phpclasses.org/browse/package/2360.html
http://phpldapadmin.cvs.sourceforge.net/phpldapadmin/phpldapadmin/lib/ldif_functions.php?view=markup</description>
   <pubDate>Fri, 24 Nov 2006 00:38:15 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t26602</link>
  </item>
  <item>
   <title>Bounty added:
http://horde.org/bounties/details.php#turba_l</title>
   <description>Bounty added:
http://horde.org/bounties/details.php#turba_ldif</description>
   <pubDate>Wed, 20 Dec 2006 17:03:15 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t27661</link>
  </item>
  <item>
   <title>Here is the first cut of the patch that supports import and </title>
   <description>Here is the first cut of the patch that supports import and export.  It only works with mozilla LDIF files.  When exporting turba to LDIF, the homeAddress value is put into the homeStreet attribute without any attempt to break up the components of the address.  The same holds true for the workAddress and street attributes.  Is export actually needed given that export is not supported for pine and mulberry address books?</description>
   <pubDate>Sun, 21 Jan 2007 22:29:49 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t28788</link>
  </item>
  <item>
   <title>Needed? I don't know, I don't even need LDIF import. ;-) Som</title>
   <description>Needed? I don't know, I don't even need LDIF import. ;-) Some people might find it is useful, for example to migrate an addressbook from SQL to LDAP.
Anyway, the default Turba SQL scheme is only one of many possible, and we should at least support all elements from config/attributes.php that have counterparts in LDIF. Addresses don't necessarily have to be in one large text field.</description>
   <pubDate>Mon, 22 Jan 2007 05:22:50 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t28792</link>
  </item>
  <item>
   <title>We now support all elements from config/attributes.php that </title>
   <description>We now support all elements from config/attributes.php that have counterparts in LDIF.
If addresses in Turba are split out, there is a one-to-one mapping to LDIF.  If they are not split out, the address is stored in one field, mozillaWorkStreet2 or mozillaHomeStreet2.</description>
   <pubDate>Sun, 18 Feb 2007 16:19:05 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t29591</link>
  </item>
  <item>
   <title>I have still have a few things I would like to see changed:</title>
   <description>I have still have a few things I would like to see changed:
- Please use &quot;Copyright 2007 The Horde Project (http://www.horde.org/)&quot; for the file header.
- Add a BC check in Turba so that the LDIF features will only be used with an recent enough Horde version.
- Always use curly braces.
- Is it possible to reduce the large &quot;case&quot; lists, i.e. by making them the &quot;default&quot; case, using in_array(), or similar?</description>
   <pubDate>Mon, 19 Feb 2007 04:49:58 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t29602</link>
  </item>
  <item>
   <title>&gt; I have still have a few things I would like to see changed</title>
   <description>&gt; I have still have a few things I would like to see changed:
&gt; - Please use &quot;Copyright 2007 The Horde Project
&gt; (http://www.horde.org/)&quot; for the file header.  

Done.

&gt; - Always use curly braces.  

Done.  

&gt; - Is it possible to reduce the large &quot;case&quot; lists, i.e. by making 
&gt; them the &quot;default&quot; case, using in_array(), or similar?  

Done.

&gt; - Add a BC check in Turba so that the LDIF features will only be used 
&gt; with an recent enough Horde version.  

Should this be moved to a Turba_Data package since it is very Turba specific?  
</description>
   <pubDate>Mon, 26 Feb 2007 22:20:31 -0500</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t29816</link>
  </item>
  <item>
   <title>&gt;&gt; - Add a BC check in Turba so that the LDIF features will </title>
   <description>&gt;&gt; - Add a BC check in Turba so that the LDIF features will only be used
&gt;&gt; with an recent enough Horde version.
&gt;
&gt; Should this be moved to a Turba_Data package since it is very Turba specific?

I moved the LDIF class to turba/lib/Data to avoid the BC issue.</description>
   <pubDate>Thu, 15 Mar 2007 23:10:10 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t30385</link>
  </item>
  <item>
   <title>Committed, thanks! I tweaked the handling of workAddress and</title>
   <description>Committed, thanks! I tweaked the handling of workAddress and homeAddress in ldif.php, let me know if you have any questions about that. As I said to Matt on IRC I'd like to see a test for this so we can verify that at least the basic case works (just transform a piece of data and make sure it comes out right, not worrying about saving to Turba).</description>
   <pubDate>Sat, 17 Mar 2007 22:46:35 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/2506#t30439</link>
  </item>
  

 </channel>
</rss>
