AddressBook

 view release on metacpan or  search on metacpan

html/index.html  view on Meta::CPAN

  <li><a href="http://perl-abook.sourceforge.net/ChangeLog">Change History</a>
  <li><a href="http://www.sourceforge.net/projects/perl-abook">perl-abook project page</a>
  <li><a href="http://sourceforge.net/mail/?group_id=9692">perl-abook-tech mailing list</a>
  <li><a href="http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi?cvsroot=perl-abook">perl-abook-tech CVS</a>
</ul>
<hr>
<h3>Features</h3>
<ul>
  <li>Configurable attribute mapping
  <li>Simple methods for moving entries between backend databases.
  <li>Entries can be <a href=AddressBook.html#sync>synchronized</a> between backend 
databases of different types.
  <li>Attributes can be calculated "on the fly" (e.g. based on other attributes).
</ul>
<hr>
<h3>Requirements</h3>
<p>The following perl library modules are required:
<ul>
  <li>XML::DOM
  <li>Date::Manip
</ul>

html/index.html  view on Meta::CPAN

Also configuration file information.
</ul>
<p>See also the man pages for the <a href=#backend_doc>different backend databases</a>.
<hr>
<h3>Examples</h3>
<p>The following sample files are provided in the examples directory. 
<font color=red>Note:  It is highly recommended that you back up your addressbook database 
before running one of these scripts.</font>
<table>
  <tr><td>ldap-abook.conf<td>A sample configuration file which is used by all of the sample scripts
  <tr><td>abook.palm<td>A PalmOS conduit which synchronizes a palm pilot with an LDAP database.
  <tr><td>SyncAbook<td>Same as abook.palm, but written as a <a href=http://www.moshpit.org/>PilotManager</a> 
conduit.
  <tr><td>phonelist.cgi<td>A cgi script which will generate a list of names and phone numbers from
an LDAP database.
</table>
<hr>
<h3>See Also</h3>
<p>The <a href=http://ldap-abook.sourceforge.net>LDAP-Abook Project</a> is a full-featured
CGI interface, designed to work with an LDAP backend addressbook database.  LDAP-Abook is based
on the perl-abook library.

lib/AddressBook.pm  view on Meta::CPAN

=item 3

Each record of the master is added to the slave

=back

The 'merging' of the master and slave entries involves taking each attribute in the
slave's entry and replacing the corresponding attribute in the master's entry.  
Note that attributes that are deleted only on the slave are therefore effectively ignored 
during synchronization.

Similarly, deletions made on the slave database are effectively ignored during
synchronization.

=cut

sub sync {
  my %args = @_;
  my $master = $args{master};
  my $slave = $args{slave};
  unless ($master->{key_fields} && $slave->{key_fields}) {
    croak "Key fields must be defined for both master and slave backends";
  }

lib/AddressBook/DB/PDB.pm  view on Meta::CPAN

=head1 Deleted Records

PDB records which have the "deleted" flag set are removed as part of the initialization
process.  The "archive" flag is ignored. 

=head1 Categories

For convienience, a record's category is treated like any other attribute.  New
categories are created as necessary.  Moving a record to a new category will achieve
the expected result during synchronization.
However, because renaming a category does
not cause affected records to be marked as "modified", category renaming operations will
be lost during synchronization.  

=head1 AUTHOR

David L. Leigh, <dleigh@sameasiteverwas.net>

=head1 SEE ALSO

L<AddressBook>,
L<AddressBook::Config>,
L<AddressBook::Entry>.