Lenora, At my library, we use Branches for "physical buildings", and Shelving Locations (authorized value LOC, items.location, or MARC 952$c) to denote which area of the library the material is in. Downside: all our libraries wind up having the same available shelving locations, even if the location is specific to our main branch (like a unique collection's stacks). There is an additional, somewhat mysterious parameter called 'stack' (authorized value STACK, items.stack, 952$j), which I'm not sure how to use. Anyone have any experience with it? Hope this helps, Ian Walls Systems Integration Librarian NYU Health Sciences Libraries 550 First Ave., New York, NY 10016 (212) 263-8687 -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Lenora Oftedahl Sent: Thursday, December 10, 2009 11:25 AM To: KOHA Subject: Re: [Koha] Holding v. Home branch I use homebranch for the physical address where the book is located and then the holding branch for a shelving location as I have a couple of different places where materials are shelved: location and sublocation. Is there a better way to delineate where books are shelved? Thanx. Lenora Lenora A. Oftedahl StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. =================================