[prev in list] [next in list] [prev in thread] [next in thread]
List: openldap-software
Subject: evolutionPerson, zillaPerson and 'description'
From: "Brian K. Jones" <jonesy () CS ! Princeton ! EDU>
Date: 2003-02-28 20:59:06
[Download RAW message or body]
Hi again.
I'm working on getting the very last attribute for my schema working.
It's giving me huge probelms. Here's the short version:
core.schema defines the attributetype 'description' which is what the
Mozilla address book uses to display the 'other' field in the 'Card'
view of the search results. (Hope I'm clear there).
evolutionperson.schema defines the attributetype 'note' which is
functionally and syntactically equal to 'description'. It's what
evolution uses to get the 'Notes' part of a contact card.
So I figured I could map evolution's 'note' to core's 'description',
like this:
attributetype ( 2.5.4.13 NAME ( 'description' 'note' )
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} )
However, doing this only returns results in Mozilla (description) - not
Evo (note). Reversing the order of the attribute names in the
core.schema file reverses the result - Evo works, and not Mozilla.
Has anyone seen this issue before? Any clues are much appreciated.
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/1.1.6">
</HEAD>
<BODY>
Hi again.<BR>
<BR>
I'm working on getting the very last attribute for my schema working. It's \
giving me huge probelms. Here's the short version:<BR> <BR>
core.schema defines the attributetype 'description' which is what the Mozilla address \
book uses to display the 'other' field in the 'Card' view of the search results. \
(Hope I'm clear there).<BR> <BR>
evolutionperson.schema defines the attributetype 'note' which is functionally and \
syntactically equal to 'description'. It's what evolution uses to get the \
'Notes' part of a contact card. <BR> <BR>
So I figured I could map evolution's 'note' to core's 'description', like this:<BR>
<BR>
attributetype ( 2.5.4.13 NAME ( 'description' 'note' )<BR>
EQUALITY caseIgnoreMatch<BR>
SUBSTR caseIgnoreSubstringsMatch<BR>
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} \
)<BR> <BR>
However, doing this only returns results in Mozilla (description) - not Evo \
(note). Reversing the order of the attribute names in the core.schema file \
reverses the result - Evo works, and not Mozilla. <BR> <BR>
Has anyone seen this issue before? Any clues are much appreciated.
</BODY>
</HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic