in the directory is not an all-or-nothing operation, it can be performed over a period of time and without service disruption.

•Using multiple virtual DIT views for navigation and management allows for more flexible use of the directory service.

With the functionality provided by virtual DIT views, an organization can use both the old and new methods to organize directory data without any requirement to place entries at certain points in the DIT.

•Virtual DIT view hierarchies can be created as a kind of ready-made query to facilitate the retrieval of commonly-required information.

•Views promote flexibility in working practices and reduce the requirement that directory users create complex search filters, using attribute names and values that they would otherwise have no need to know.

The flexibility of having more than one way to view and query directory information allows end users and applications to find what they need intuitively through hierarchical navigation.

4.4.3Example of virtual DIT views

The LDIF entries below show a virtual DIT view hierarchy that is based on location. Any entry that resides below dc=example, dc=com and fits the view description appears in this view, organized by location.

dn: ou=Location Views, dc=example,dc=com

objectclass: top

objectclass: organizationalUnit

objectclass: nsView

ou: Location Views

description: views categorized by location

dn: ou=Sunnyvale, ou=Location Views, dc=example,dc=com

objectclass: top

objectclass: organizationalUnit

objectclass: nsView

ou: Sunnyvale nsViewFilter: (l=Sunnyvale)

description: views categorized by location

dn: ou=Santa Clara, ou=Location Views, dc=example,dc=com

objectclass: top

objectclass: organizationalUnit

objectclass: nsView

ou: Santa Clara

nsViewFilter: (l=Santa Clara)

description: views categorized by location

dn: ou=Cupertino, ou=Location Views, dc=example,dc=com

objectclass: top

objectclass: organizationalUnit

objectclass: nsView

ou: Cupertino

nsViewFilter: (l=Cupertino)

description: views categorized by location

A subtree search based at ou=Location Views, dc=example, dc=com would return all entries below dc=example,dc=com which match the filters (l=Sunnyvale), (l=Santa Clara), or (l=Cupertino). Conversely, a one-level search would return no entries other than the child view entries because all qualifying entries reside in the three descendant views.

The ou=Location Views, dc=example, dc=com view entry itself does not contain a filter. This feature facilitates hierarchical organization without the requirement to further restrict the entries contained in the view. Any view may omit the filter. Although the example filters are very simple, the filter used can be as complex as necessary.

54 Designing the directory tree