<html>
<body>
If you are talking about the staff use (as opposed to the tech stuff),
there is another way of approaching your problem.<br><br>
I count three (or four) main places in an item records where you can
enter hierarchical information that will show up in other places in your
catalog that both patrons and staff can see. I would use a combination of
these fields to best fit your situation.<br><br>
I'm a little unsure about the interactions in your scenario about using
both Location (952a) and Sublocation (952b). It's possible they could
represent your "library, departments and laboratories" and
"several sublocations/collections" respectively.<br><br>
However, if you use your 952a (Location) for your "whatever your
institution or entity is", you can subdivide otherwise as
follows.<br><br>
library, departments and laboratories -- these could all be assigned a
shelving location (952c)
<ul>
<li>Library
<li>Chemistry Dept.
<li>Physics Lab
</ul>several sublocations/collections -- the next level could be a
collection (952 subfield 8).<br><br>
A further breakdown can be done using the call number (952o)
<ul>
<li>Smith office 628.3
<li>Staff Lounge 628.3
</ul>Volume numbers and years go best in 952h for us.<br><br>
Using these areas, you have quite a bit of flexibility, depending on your
actual situation.<br><br>
So, let's take a hypothetical book that is housed in the Chemistry Dept.
of "Your Local University Library Collection."<br><br>
Location: Your Local University Library Collection<br>
Shelving location: Chemistry Dept.<br>
Collection: Faculty offices<br>
Call number: Smith 628.3<br>
Volume: v. 3<br><br>
I'd cut out the Collection use like this, if you don't need that many
levels.<br><br>
Hope that gives you another perspective.<br><br>
Kathy<br>
<br><br>
<br><br>
At 02:39 PM 12/11/2008, Lino Tremblay wrote:<br>
<blockquote type=cite class=cite cite="">Hello everybody,<br><br>
I'm trying to figure out how I'll set up my locations, and I'd like to
<br>
know how you guys did. As our situation not atypicall, I'm sure some of
<br>
you have faced the same problem<br><br>
So: we have several collections here, located for the most part in three
<br>
places: library, departments and laboratories. Each of these locations
<br>
is divided in several sublocations/collections. My problem is that all
<br>
locations/sublocations/collections in Koha are at the same level: in an
<br>
item, I could choose "Library" as a location, and a specific
department <br>
as a sublocation - or the opposite, or any combination I can imagine -
<br>
and it would be accepted.<br><br>
My question now: is there a way to create a hierarchy so that my <br>
Location menu contains only my three locations, and the <br>
Sublocation/collection shows only the collections available within this
<br>
location? Or at least refuse an invalid combination?<br><br>
<br>
Thanks!<br><br>
Lino<br>
_______________________________________________<br>
Koha mailing list<br>
Koha@lists.katipo.co.nz<br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" eudora="autourl">
http://lists.katipo.co.nz/mailman/listinfo/koha</a></blockquote></body>
<br>
<body>
<font face="Comic Sans MS" size=2>Kathleen D. Rippel<br>
Pathfinder Central, Manager<br>
Central Kansas Library System<br>
1409 Williams<br>
Great Bend, KS 67530<br><br>
(620-792-4865) phone<br>
(800-362-2642) toll-free, KS<br>
(620-792-5495) fax<br><br>
kdr@ckls.org</font></body>
</html>