Do you have a need for sub-branches within Koha?
Hi I was wondering wether there are other libraries, particularly corporate or specialty libraries who have a need (or could see one :-) for sub branches. The context for this is a Branch which is the office building in a city - eg Wellington And then a sub branch which is the third floor. This would be quite a lot of stuff to "touch" in Koha - specifically it would involve changing circulation and I think adds a layer of complexity perhaps to issuing and returning items. On the other hand I'd imagine that the libraies who would use this wouldn't do that much issuing and returning? SO thoughts pleasa? Is it a useful idea? Does anyone do it already? Cheers Rachel -- _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications MANAGING DIRECTOR Ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org
On 2004-09-23 07:39:28 +0100 Rachel Hamilton-Williams <rachel@katipo.co.nz> wrote:
I was wondering wether there are other libraries, particularly corporate or specialty libraries who have a need (or could see one :-) for sub branches. [...] On the other hand I'd imagine that the libraies who would use this wouldn't do that much issuing and returning?
Yes, I think libraries with locations/branches and offices/subbranches are more likely to transfer books between subbranches often, instead of actually issue them. This is a case which someone discussed with me in the past, but koha isn't really ready for in 2.0. -- MJR/slef My Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ LinuxExpo.org.uk village 6+7 Oct http://www.affs.org.uk
Rachel Hamilton-Williams a écrit :
Hi
I was wondering wether there are other libraries, particularly corporate or specialty libraries who have a need (or could see one :-) for sub branches.
The context for this is a Branch which is the office building in a city - eg Wellington
And then a sub branch which is the third floor.
This would be quite a lot of stuff to "touch" in Koha - specifically it would involve changing circulation and I think adds a layer of complexity perhaps to issuing and returning items.
On the other hand I'd imagine that the libraies who would use this wouldn't do that much issuing and returning?
SO thoughts pleasa? Is it a useful idea? Does anyone do it already?
Yes, me ;-) It's the "location" field in the items table (new in 2.1.1 iirc, maybe 2.1.2) See the log of my updatedatabase CVS commit from sep, ; Modified Files: updatedatabase Log Message: adding a "location" field to the library. This field is useful when the callnumber contains no information on the room where the item is stored. With this field, we now have 3 levels of informations to find a book : * the branch. * the location. * the callnumber. This should be versatile enough to solve any storing method. This hack is quite simple, due to the nice Biblio.pm API. The MARC => koha db link is automatically managed. Just add the link in the parameters section. Enjoy ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
We've reeding your mail and example, and found that we didn't realised of instituions with that problem. Then we remeberd that a local ingeniering school has this reality, and you have sub branches within the school (phisics, electrical ingeniering, informatics, ...). As far as I'm aware they are happy with their ILS and not planning to migrate to koha. Rachel Hamilton-Williams wrote:
Hi
I was wondering wether there are other libraries, particularly corporate or specialty libraries who have a need (or could see one :-) for sub branches.
The context for this is a Branch which is the office building in a city - eg Wellington
And then a sub branch which is the third floor.
This would be quite a lot of stuff to "touch" in Koha - specifically it would involve changing circulation and I think adds a layer of complexity perhaps to issuing and returning items.
On the other hand I'd imagine that the libraies who would use this wouldn't do that much issuing and returning?
SO thoughts pleasa? Is it a useful idea? Does anyone do it already?
Cheers Rachel
participants (4)
-
Andres Tarallo -
MJ Ray -
Paul POULAIN -
Rachel Hamilton-Williams