From users-return-3929-apmail-directory-users-archive=directory.apache.org@directory.apache.org Wed Jun 15 06:23:34 2011 Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EC9764B7C for ; Wed, 15 Jun 2011 06:23:34 +0000 (UTC) Received: (qmail 82196 invoked by uid 500); 15 Jun 2011 06:23:34 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 82085 invoked by uid 500); 15 Jun 2011 06:23:23 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 81948 invoked by uid 99); 15 Jun 2011 06:23:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jun 2011 06:23:19 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prvs=140fe538c=manish.kutaula@tcs.com designates 121.242.48.3 as permitted sender) Received: from [121.242.48.3] (HELO inblrg01.tcs.com) (121.242.48.3) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jun 2011 06:23:13 +0000 X-IronPort-AV: E=Sophos;i="4.65,368,1304274600"; d="scan'208";a="46878189" X-DISCLAIMER: FALSE In-Reply-To: References: To: users@directory.apache.org MIME-Version: 1.0 Subject: Re: Storing conference room details, advice needed X-KeepSent: 4BEDD831:6DDB03ED-652578B0:0022E3FF; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.2FP1 November 30, 2010 Message-ID: From: Manish Kutaula Date: Wed, 15 Jun 2011 11:52:44 +0530 X-MIMETrack: Serialize by Router on InBlrM14/TCS(Release 8.5.2FP1|November 29, 2010) at 06/15/2011 11:52:50, Serialize complete at 06/15/2011 11:52:50 Content-Type: multipart/alternative; boundary="=_alternative 002309FF652578B0_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 002309FF652578B0_= Content-Type: text/plain; charset="US-ASCII" Hi jim, I didnot get the idea of making each resource as a objectClass. Having a multi-valued attribute in conference class to hold the resources is fine. Manish Kutaula From: Jim Willeke To: users@directory.apache.org Date: 06/14/2011 07:39 PM Subject: Re: Storing conference room details, advice needed Without a lot of details as to how your specific operation works, I think I would create each "resource" as an objectClass and then have a multi-valued attribute on the conference room for resources which is of DN syntax. This would allow you to move resources from one conference room to another. -jim Jim Willeke On Tue, Jun 14, 2011 at 7:10 AM, Manish Kutaula wrote: > Hi, > > i have a requirement that i have to store conference room details in > apacheds server. For this i have created a new object class and attributes > to store the details of conference room which are: > > roomName: > capacity: > availability: > location: > description > building > floor > > I have one more requirement in which i have to store the resources of > conference room i.e. audio/video facility, speaker phone, bridge etc. > how can i store these resources, one possible solution can be that i make > a resource type attribute and make it multi-valued and store the values in > it. > > Finally, i have to retrieve the data from apacheds server and generate a > xml for it. > > what can be the most practical solution for it. any quick ideas will be > helpful. > > Thanks, > --Manish Kutaula > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > --=_alternative 002309FF652578B0_=--