Project

General

Profile

Bug #150

find a way to name non-unique items

Added by Marc Dequènes about 10 years ago.

Status:
New
Priority:
Normal
Category:
LDAP :: Abstraction
Target version:
Start date:
2010-09-08
Due date:
% Done:

0%

Estimated time:
Patch Available:
No
Found in Versions:
Confirmed:
No
Branch:
Help Needed:

Description

(examples with the MilkyPond world)

If individuals are unique accross the whole database, it could be nice to limit this unicity to unit/People and allow user's address books. So, individual/duck may have several address books under its entry, and possibly with duplicated contacts. We will end-up with individual/toto being in several places, and with to way to select the right one to manipulate. We need to find a way to specify these kind of entries in a simple way.

Something like this could do:
  • unit/People:individual/toto
  • individual/duck:addressbook/mycontacts1:individual/toto
  • individual/duck:addressbook/mycontacts2:individual/toto

It is a bit lenghty, but ensure proper unicity in all cases. it would be necessary to discover the shortest handle-path for search results. The big problem with this solution is the handle-path is not persistent during time : unit/People:individual/toto will still be valid, but individual/toto would be the shortest path if the two others disappear (and the reversed situation would be even worse).

Also available in: Atom PDF