36 |
=head1 LDAP |
=head1 LDAP |
37 |
|
|
38 |
Implement LDAP entry and edit interface (insteresting problem since most |
Implement LDAP entry and edit interface (insteresting problem since most |
39 |
values can have multiple entries which doesn't map nicely to relational |
entries can have multiple values which doesn't map nicely to relational |
40 |
schema) |
schema). |
41 |
|
|
42 |
|
=head2 Multiple values |
43 |
|
|
44 |
|
When creating records with ARRAY values C<A3C::Record/create> |
45 |
|
joins values with magic marker between them to make rest of Jifty happy. |
46 |
|
|
47 |
|
Plan is to use full-text search engine to search over data anyway, so this |
48 |
|
is not serious limitation. If needed, something like bitmap indexes could be |
49 |
|
used at database level to expose thouse values for filtering. For joins we |
50 |
|
would probably need separate materialized many-many tables which could be |
51 |
|
created more-or-less automatically in L<A3C::Record>. |
52 |
|
|
53 |
This can in turn be broken down into following tasks: |
This can in turn be broken down into following tasks: |
54 |
|
|
55 |
=head2 Import data from existing LDAP server |
=head2 Import data from existing LDAP server |
56 |
|
|
57 |
C<bin/import-ldap.pl> has embedded documentation |
C<bin/import-ldap.pl> has embedded documentation and uses <A3C::LDAP> |
58 |
|
|
59 |
|
L<http://a3c.skole.hr/ldap/> is user interface to L<A3C::View::LDAP> and |
60 |
|
L<A3C::Action::SyncOrganization> |
61 |
|
|
62 |
=head2 Query existing LDAP server |
=head2 Query existing LDAP server |
63 |
|
|