Re: Different Libraries sharing a common Innopac server

[Josh Stompro <stomproj at larl dot org>]

Our Millennium system has 2 different library systems with multiple 
branches.  I have found that the system wasn't designed with this in 
mind at all and it causes problems that are annoying to work around.  We 
have the consortia module and it really feels tacked on.  Instead of 
having a logical hierarchical setup where each location code would 
belong to a certain system, they add 2 extra fields to each patron 
record and one extra field to each item record that says which system it 
belongs to.
   And trying to do anything for just one system at a time is also a 
pain.  We need to run notices centrally for each system and the only way 
to do it is to setup a location served group with all the systems 
location codes in it.  But the requesting system fails to work properly 
when there is a location served group will the same location codes as 
other locations served groups.  So we have to create and delete these 
groups whenever we need to run overdues, and any requests placed while 
those are active will ignore the library priority list.

   I'm sorry about the rant  All opinions expressed are my own.
Josh

Alan Bartlett wrote:

> Hi,
>
>     I am interested in talking with someone who is in the situation of 
> two libraries sharing a common server, but the libraries have 
> different barcodes for materials.  I am exploring a branch library 
> context where we want to keep the transactions separate between the 
> two locations.
>
>     Alan E. Bartlett
>
> --
> This message was distributed through the Innovative Users Group 
> INNOPAC list
> Public replies:  INNOPAC at innopacusers dot org
> Update your subscription options: 
> http://innopacusers.org/mailman/listinfo/innopac


--
--
Josh Stompro             | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857